LAX04FA291 · Cessna 172M
Cessna 172M · Accident: loss of control in flight during initial climb
From Yuba City, CA to Napa County Airport (APC)
Event
- NTSB case
- LAX04FA291
- 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
- Unknown
- 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
- C-GTKX
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Yuba City, CATo Napa County Airport (APC), Napa, 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
- Initial climb
- 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
- 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 › Airspeed, not obtained/maintained
- Pilot in command › Stall, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane collided with a sign, then stalled and impacted terrain while attempting a takeoff from a residential street. The street was about 2,000 feet in total length with a cul-de-sac on each end. Radar data showed that the airplane flew parallel to an airport runway about a mile to the west and then made a 630-degree turn (1 3/4 turns) over the accident area. The airplane landed toward the south on the road located in a housing development that was under construction and taxied back to the the north until it reached a parked semi truck that was about 1,300 feet from the south end of the road. The airplane then turned around facing the south. Witnesses said the the airplane momentarily stopped, with the engine revving, then it began to roll down the road and subsequently became airborne. During the initial climb, the airplane's left wing impacted a sign, and as it approached a power line pole, the nose pitched up. About 40 to 60 feet above ground level the airplane stalled and nose-dived toward the terrain. There was no evidence of premishap mechanical malfunctions observed during the examination of the engine and airframe. According to friends of the pilot, he could not hear the stall warning horn due to a hearing impairment condition.
Probable cause
the pilot's failure to attain and maintain an adequate airspeed, which resulted in a stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04FA291
- Event ID
- 20040828X01304
- Case number
- LAX04FA291
- 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, coordinates. 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: 4828100ab20d0f554318054aa71d3dcf889aa2e9f82ed3b5ebc5376ece149531; retrieved 2026-09-20T18:22:29.527Z.