ERA24LA030 · Cessna 172 M
Southern Aero Cessna 172 M · Accident: loss of control in flight en route
From Okeechobee County Airport (OBE) to Miami Homestead General Aviation Airport (X51)
Event
- NTSB case
- ERA24LA030
- 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
- 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
- Visual Meteorological Cond
Cessna 172 M
- Aircraft type
- Cessna 172
- 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
- N140FS
- Operator
- Southern Aero
- Onboard fatalities
- Unknown
- Route
- From Okeechobee County Airport (OBE), Okeechobee, FLTo Miami Homestead General Aviation Airport (X51), Homestead, FL
- Aircraft age
- About 50 years (built 1973)
- 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
- 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
- Loss of control in flight
- 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
- Personnel issues › Physical
- 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 non-instrument-rated private pilot had previously scheduled a night flight with a safety pilot in another airplane, but the safety pilot was unable to go. The pilot departed on the first leg of the night flight and landed at the destination airport uneventfully. He then departed for the return flight. The pilot reported that, while flying over a non-populated area with no ground reference lights, he experienced altitude deviations that he attributed to spatial disorientation, which was exacerbated by self-reported fatigue. After entering a cloud, the airplane began a right turn while descending, completing multiple right turns with a decreasing turn radius. The airplane subsequently impacted the marshy terrain below. The pilot was able to self-extricate from the wreckage and was rescued more than 6 hours later. Following the accident, the pilot confirmed there was no mechanical failure or malfunction of the airplane’s flight controls. Given this information, during cruise flight at night, over an area with no ground reference lights and after encountering a cloud, the pilot experienced spatial disorientation that was exacerbated by the effects of fatigue. The airplane then entered a right descending turn that was unarrested by the pilot, and that continued to ground contact. Had a safety pilot been present, it is possible that the pilot’s spatial disorientation could have been recognized before it developed into the terminal descent. Personnel from flight school who operated the airplane stated that they were not aware that the pilot was flying the airplane at the time of the accident flight, so it was not immediately apparent to them that the airplane was overdue. Additionally, the pilot did not request flight following services from air traffic control, contrary to the flight school’s recommendation. In addition, the airplane’s 406 MHz emergency locator transmitter (ELT) signal was not detected by the applicable monitoring satellite after the accident, likely due to radio signal attenuation as a result of the ELT’s antenna being partially submerged in water. All of these factors likely contributed to the considerable delay in initiating search and rescue efforts following the accident.
Probable cause
The pilot’s loss of airplane control and descent into terrain due to spatial disorientation during a solo night cross country flight. Contributing to the accident was the pilot’s self-reported fatigue.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA030
- Event ID
- 20231102193342
- Case number
- ERA24LA030
- 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: investigation status, coordinates, cause areas. 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: 80fdf317652c3685c19f2384fc75b5cbfd44316e474236e476cb19397de5da86; retrieved 2026-09-16T18:16:11.938Z.