ATL06LA134 · Cirrus Design Corp SR22-GTS
Cirrus Design Corp SR22-GTS · Accident: loss of control in flight en route
From Athens Ben Epps Airport (AHN) to Fort Lauderdale Executive Airport (FXE)
Event
- NTSB case
- ATL06LA134
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cirrus Design Corp SR22-GTS
- Aircraft type
- Cirrus SR22
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N518SR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Athens Ben Epps Airport (AHN), Athens, GATo Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, FL
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/spin
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Airspeed(vs), not maintained
- Pilot in command › Oxygen system, not used
- Stall/spin › Inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane experienced an in-flight loss of aircraft control during cruise flight. The pilot initially reported a turbulence encounter at 9,500 feet, and that he saw damage on the upper surface of both wings. He did not recall a significant loss of altitude or loss of control. Data downloaded from the flight displays after the event indicated that the airplane actually climbed to 15,400 feet above mean sea level (msl), nearly 17,500 feet density altitude, which was the maximum operating altitude for the airplane. The airplane then slowed, stalled, and began a rapid descent, losing 13,000 feet of altitude in about 40 seconds before recovering. During recovery, the airplane had an average of more than 4 Gs vertical loading for more than 20 seconds. Such loading would likely have resulted in G-induced loss of consciousness (G-LOC) or near-loss of consciousness. The pilot's apparent failure to accurately recall the events of the flight is likely a result of the confusion associated with hypoxia, and the subsequent confusion and amnesia associated with G-LOC or near G-LOC. It is unclear exactly why the pilot chose to increase his altitude beyond 12,500 feet msl, above which oxygen use would have been required after 30 minutes. Regardless, he continued to climb the airplane above 14,000 feet msl, an altitude above which oxygen use would have been required by the pilot regardless of the time spent at that altitude, and he subsequently climbed to above 15,000 feet, at which point oxygen use would have been required by all occupants. The pilot confirmed that neither he nor his passengers used supplemental oxygen during the flight. Examination of the airplane found no evidence of mechanical failure or malfunctions that would have prevented the airplane from operating normally.
Probable cause
The pilot's failure to use supplemental oxygen where required, and his failure to maintain sufficient airspeed to avoid a stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL06LA134
- Event ID
- 20061031X01575
- Case number
- ATL06LA134
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 11b902d228ea87974c2180cbebd8d1db6c92bc03b5444860f741140e74a40596; retrieved 2026-09-22T04:32:01.466Z.