LAX86LA213 · Cessna 172M
Cessna 172M · Accident: in flight collision with object on approach
From Fall River Mills Airport (O89) to an unrecorded destination
Event
- NTSB case
- LAX86LA213
- 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 172M
- 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
- N4450R
- Operator
- Charles Hupp
- Onboard fatalities
- Unknown
- Route
- From Fall River Mills Airport (O89), Fall River Mills, CATo not recorded
- 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
- Approach · VFR go-around
- 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
- In flight collision with object
- 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
- Tree(s)
- 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 › Altitude, misjudged
- Pilot in command › Directional control, not maintained
- Pilot in command › Raising of flaps, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED DUE TO SEVERE TURBULENCE HE DECIDED TO LAND LONG. UPON REALIZING THAT THE AIRPLANE WAS TOO HIGH HE ADDED FULL FLAPS. SHORTLY AFTER TOUCHDOWN THE PLT BEGAN TO LOSE CONTROL OF THE AIRPLANE AND ELECTED TO TAKEOFF. DURING THE INITIAL CLIMB THE AIRPLANE DID NOT ACCELERATE AND ITS RATE OF CLIMB WAS 'SLOW.' REALIZING THAT A CRASH WAS INEVITABLE THE PLT ELECTED TO 'STALL THE AIRPLANE' INTO SOME TREES. THE PLT REPORTED THAT HE DID NOT RETRACT THE FLAPS WHEN HE INITIATED THE TAKEOFF.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX86LA213
- Event ID
- 20001213X33593
- Case number
- LAX86LA213
- 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 1986-05-09.
- API snapshot SHA-256: df7aabb435a4d42f6ae73d85afd0358fdd967fd306a4c8130d5c5dfed3ded8ba; retrieved 2026-09-22T01:26:55.055Z.