Papers › Can we predict the impact conditions of meter-sized meteoroids?
Can we predict the impact conditions of meter-sized meteoroids?
Jorge I. Zuluaga, Pablo A. Cuartas-Restrepo, Jhonatan Ospina, Mario Sucerquia
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
Every year, a few metre-sized meteoroids impact the atmosphere of the Earth. Most (if not all) of them are undetectable before the impact. Therefore, predicting where and how they will fall seems to be an impossible task. In this letter we show compelling evidence that we can constrain in advance, the dynamical and geometrical conditions of an impact. For this purpose, we analyse the well-documented case of the Chelyabinsk (Russia) impact and the more recent and smaller Vi\~nales (Cuba) event, whose conditions we estimate and provide here. After using the {\em Gravitational Ray Tracing} algorithm (GRT) to "predict" the impact conditions of the aforementioned events, we find that the speed, incoming direction and (marginally) the orbital elements of the corresponding meteoroids could be constrained in advance, starting only on one hand, with the geographical location and time of the impact, and on the other hand, with the distribution in configuration space of Near Earth Objects (NEOs). Any improvement in our capability to predict or at least to constrain impact properties of medium-sized and large meteoroids, will help us to be better prepared for its potentially damaging effects.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections