LAX88LA320 · Cessna 172N
Cessna 172N · Accident: airframe, component or system failure during takeoff
From an unrecorded airport to Placerville Airport (PVF)
Event
- NTSB case
- LAX88LA320
- 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 172N
- 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
- N6406D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Placerville Airport (PVF), Placerville, CA
- 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 · roll/run
- 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
- Airframe, component or system failure
- 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 › Aircraft preflight, inadequate
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Lowering of flaps, premature
- Pilot in command › Precautionary landing, performed
Approximate · Estimated position: the centre of Truckee, CA, the place the record names. Not the accident site.
NTSB narrative
DURING TAKEOFF ROLL THE PILOT HEARD A BANGING NOISE ON THE LEFT WING. THE PILOT CONTINUED THE TAKEOFF. AT 100 FT A.G.L. HE EXECUTED A 180 DEGREE TURN TO THE RIGHT TO RETURN TO LAND. THE PILOT ADDED 30 DEGREES OF FLAPS TO THE 10 THAT HAD BEEN SET FOR TAKEOFF. THE ACFT BEGAN TO DESCEND AND THE PILOT COULD NOT STOP THE DESCENT. HE LANDED THE ACFT IN AN OPEN FIELD. DURING THE LANDING THE NOSE WHEEL COLLIDED WITH A ROCK, BROKE OFF AND THE AIRCRAFT NOSED OVER. AN EXAMINATION OF THE WRECKAGE REVEALED THAT THE LEFT FUEL CAP WAS NOT IN PLACE AND WAS HANGING FROM THE WING BY ITS CONNECTION CHAIN. DENSITY ALTITUDE WAS ABOUT 7500 FEET.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX88LA320
- Event ID
- 20001213X26865
- Case number
- LAX88LA320
- 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. 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: c34c8bd60be62625c28213e2447a2ac4b226bd17b840778543041912db1e7a34; retrieved 2026-09-22T00:24:29.719Z.