ERA22FA083 · Cessna 182
Cessna 182 · Accident: VFR encounter with IMC during initial climb
From Statesboro Bulloch County Airport (TBR) to Zephyrhills Municipal Airport (ZPH)
Event
- NTSB case
- ERA22FA083
- 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
- 1 · all aircraft and ground
- Ground fatalities
- 0
- 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
- Instrument Meteorological Cond
Cessna 182
- Aircraft type
- Cessna 182
- 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
- N5776B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Statesboro Bulloch County Airport (TBR), Statesboro, GATo Zephyrhills Municipal Airport (ZPH), Zephyrhills, FL
- Aircraft age
- About 65 years (built 1956)
- 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
- Initial climb
- Defining eventThe 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
- VFR encounter with IMC
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The instrument-rated commercial pilot had conducted a cross-country flight to the airport arriving in the afternoon and, after attending a meeting, was returning to her home airport on a night visual flight rules (VFR) cross-country flight. Before the return flight, the pilot discussed with a family member her knowledge of a low cloud layer and her intention to stay low for the first 10 to 15 miles of the flight. At the time of departure, dark night conditions prevailed, and the airport was reporting an overcast cloud ceiling at 600 ft above ground level (agl). Review of automatic dependent surveillance-broadcast (ADS-B) data found that the airplane became airborne before the midpoint of the runway and turned right toward the destination airport. It then climbed to about 1,000 ft mean sea level (msl), which was about 800 ft agl, before entering a left turn about 2 miles south of the airport. The airplane continued in a left 360° tightening turn where a maximum altitude of about 1,800 ft msl was reached, which was subsequently followed by a rapid descent. Before the left 360° turn, the airplane likely entered the low cloud layer and never exited the clouds until a few seconds before it impacted with terrain. Multiple witnesses reported that the airplane’s engine noise was loud and continuous until impact. Examination of the wreckage revealed no evidence of preimpact mechanical malfunctions or failures with the airplane. Evaluation of the wreckage indicated that the airplane impacted terrain in a left turning descent at high speed. Based upon ADS-B, meteorological, and astronomical data, the pilot initiated a VFR flight into known dark night instrument meteorological conditions, which would have prevented reliable control of the airplane using external visual cues. The circling and rapidly ascending and descending flight track was consistent with a pilot who was experiencing spatial disorientation, which resulted in a loss of control in flight and a high speed impact with terrain. The pilot’s instrument and night currency could not be determined. The pilot’s toxicology report was positive for ethanol and quetiapine. Given that the ethanol was identified at a low level in muscle and that none was found in liver tissue, it is likely that the identified ethanol is from sources other than ingestion and unlikely that any effects from it contributed to the circumstances of the crash. Attempts were made to identify the underlying reason for the pilot’s use of quetiapine; however, the investigation was unable to do so. While the drug itself may cause neuropsychiatric effects, at the low levels likely present at the time of the event, it was unlikely to impair judgment. However, whether an underlying medical condition might have influenced the pilot’s decision-making could not be determined from the available information.
Probable cause
The pilot’s decision to initiate a visual flight rules flight into dark night instrument meteorological conditions, which resulted in spatial disorientation and subsequent loss of control shortly after takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22FA083
- Event ID
- 20211208104367
- Case number
- ERA22FA083
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2021-12-08.
- API snapshot SHA-256: 36c59a191141f49865f4d9a0be6c43a5448079191cfcbd9aea99c7adee127788; retrieved 2026-09-15T07:38:27.146Z.