LAX88FA307 · Cessna 172
Cessna 172 · Accident: loss of control in flight during takeoff
From an unrecorded airport to Four Corners Regional Airport (FMN)
Event
- NTSB case
- LAX88FA307
- 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
- 4 · 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
- 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
- N54814
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Four Corners Regional Airport (FMN), Farmington, NM
- 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
- Takeoff
- 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
- Destroyed
Cause areas
- Pilot in command › Stall/spin, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT HAD FLOWN THE ACFT ON TWO PREVIOUS FLIGHTS ON THE DAY OF THE ACCIDENT. THE FIRST FLT WAS WITHOUT INCIDENT. THE SECOND FLT WAS ABORTED DURING THE TAKEOFF CLIMB. THE PILOT CALCULATED HIS WEIGHT ONBOARD AND REALIZED HE EXCEEDED THE MAX GROSS. HE DEFUELED AN UNKNOWN QUANTITY OF FUEL AND PLANNED TO STAY THE NIGHT IN THE AREA BUT WAS UNABLE TO SECURE LODGING. HE THEN ELECTED TO CONTINUE THE FLT THAT NIGHT. WITNESSES STATED THE ACFT CLIMBED TO APRX 200 FT WITH THE WINGS FLUCTUATING IN BANK ANGLE AFTER WHICH THE ACFT ENTERED A SPIRAL AND DESCENDED TO THE GROUND. DENSITY ALT WAS CALCULATED TO HAVE BEEN 8,500 FT WHEN THE TAKEOFF OCCURRED. THE ARPT PROVIDES A 'BLACK HOLE' ENVIROMENT AT NIGHT. REVIEW OF THE PLT LOGBOOKS REVEALED A LACK OF RECENT NIGHT EXPERIENCE IN ACCORDANCE WITH FAR PART 61.75(D).
Probable cause
THE PILOT FAILED TO MAINTAIN CONTROL OF THE AIRCRAFT DURING NIGH VISUAL METEOROLOGICAL CONDITIONS. CONTRIBUTING TO THIS ACCIDENT WAS THE PILOT'S LACK OF RECENT EXPERIENCE AT NIGH AND THE LACK OF OUTSIDE VISUAL REFERENCES DUE TO DARKNESS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX88FA307
- Event ID
- 20001213X26847
- Case number
- LAX88FA307
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1988-09-04.
- API snapshot SHA-256: a934d529e7032320820d9de267c99553197d30a202da0ceeae8f9ad2be9b093a; retrieved 2026-09-21T03:34:56.296Z.