Azerbaijani Airlines Flight AZ8243, an Embraer 190 operating from Baku to Grozny on December 25, 2024, has drawn sustained attention from aviation analysts, investigators, and now academic researchers following its crash near Aktau, Kazakhstan. The flight became one of the most scrutinized incidents of late 2024 after evidence emerged suggesting the aircraft sustained damage consistent with Russian ground-based air defense activity while attempting to approach Grozny in instrument meteorological conditions, before crew diverted across the Caspian Sea and lost control on approach. The crash killed 38 of the 67 people on board. A Reddit post from an IB Diploma Programme student illustrates the degree to which the incident has penetrated academic discourse, with the student seeking raw ADS-B altitude and time data — specifically a CSV export typically available through FlightRadar24 premium subscriptions — to build mathematical models of the flight profile for a high school calculus coursework component.
The student's methodology, while academic in scope, mirrors the workflow that professional accident analysts and flight data monitoring (FDM) specialists apply in operational contexts. Modeling altitude-versus-time curves, fitting piecewise functions, computing first and second derivatives to extract climb and descent rates, and benchmarking against certified aircraft performance envelopes are all standard steps in post-event flight profile reconstruction. For professional pilots, this highlights a practical reality: ADS-B data captured by aggregators like FlightRadar24 and FlightAware constitutes a publicly accessible shadow record of nearly every IFR operation, and the analytical techniques being applied to AZ8243 by a high school student are the same ones used by insurers, regulators, and legal teams following incidents involving Part 135 or international air carrier operations.
Access to raw ADS-B exports remains gated behind subscription tiers on major aggregator platforms, a friction point the student explicitly notes. For professional operators, this data tier is often available through safety partnerships — FR24 offers a Business Flight Tracker product and ASIAS-linked programs provide similar access in the U.S. context — but casual access to granular CSV-level position and altitude data requires either a paid subscription, academic data-sharing agreements, or requests through official investigation channels such as those coordinated by Kazakhstan's Aviation Administration or the Interstate Aviation Committee. The AZ8243 investigation involves multiple jurisdictions and the sensitive question of Russian military involvement, which has complicated the release of definitive flight data and likely explains why clean, authoritative datasets are not freely circulating.
The broader significance of AZ8243 for working pilots and flight operations departments extends well beyond the mathematics of a descent profile. The incident reopened urgent discussions about flight operations in and around active conflict zones, NOTAM reliability for airspace adjacent to Russian territory, and the adequacy of crew and dispatcher awareness regarding MANPADS and surface-to-air threat environments. ICAO and several national aviation authorities issued guidance in the weeks following the crash reminding operators that conflict zone risk assessments must account for the possibility that military activity affecting civil aviation will not always be formally NOTAMed or disclosed in real time. Airlines and corporate flight departments operating in Eastern European, Caucasus, and Central Asian corridors are expected to treat those risk assessments with elevated scrutiny, and the AZ8243 profile — a crew executing an approach into a politically sensitive terminal area without full situational awareness of active threats — represents a scenario that flight operations manuals and dispatcher training programs must explicitly address.
The student's project also reflects a wider trend of open-source flight data analysis becoming accessible to non-specialist audiences, driven largely by ADS-B aggregators and tools like ADSBexchange, which does not filter military or sensitive traffic and does not require subscriptions for most data access. For corporate and airline operators, the democratization of this data has dual implications: it enables more robust independent safety monitoring and near-real-time performance benchmarking, but it also means that anomalous altitude deviations, airspeed exceedances, and unusual flight profiles are observable and archivable by virtually anyone with an internet connection. Flight departments that have not yet integrated ADS-B data review into their internal safety management system processes are operating with a blind spot that regulators, insurers, and increasingly, curious students with calculus textbooks, are quietly filling on their behalf.