LAX07CA256 · Cessna 150L
Cessna 150L · Accident: loss of control in flight on approach
From Keystone Heights Airport (42J) to Keystone Heights Airport (42J)
Event
- NTSB case
- LAX07CA256
- 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
- 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 150L
- Aircraft type
- Cessna 150
- 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
- N11449
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Keystone Heights Airport (42J), Keystone Heights, FLTo Keystone Heights Airport (42J), Keystone Heights, FL
- 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
- 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/mush
- 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 › Airspeed, not attained
- Pilot in command › Raising of flaps, excessive
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 landed hard on the runway during an attempted go-around, causing substantial damage. In the flare for landing the student pilot decided to do a go-around due to the effects of a wind gust. The student added full power, shut off the carburetor heat, and reduced the flaps to 10 degrees. Initially the airplane began to climb, and then "dropped and landed hard" on the runway. According to the Cessna 150L owner's manual, during a go-around, the flaps should be reduced to 20 degrees after application of full power. After a safe airspeed has been attained the flaps should be slowly retracted to the full up position.
Probable cause
the student pilot's excessive retraction of flaps and failure to attain an adequate airspeed during a go-around that led to a stall/mush.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07CA256
- Event ID
- 20071001X01484
- Case number
- LAX07CA256
- 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: d23103011564d9fb20d22b81172e9d970f4fb340068c09dc9d46605ac7818339; retrieved 2026-09-22T03:31:10.690Z.