ANC11FA055 · Cessna 150M
Cessna 150M · Accident: loss of control in flight during initial climb
From Lake Hood Airport (Z41) to Lake Hood Airport (Z41)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ANC11FA055
- 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 150M
- 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
- N66286
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Lake Hood Airport (Z41), Anchorage, AKTo Lake Hood Airport (Z41), Anchorage, AK
- 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
- Defining eventThe 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot departed from an off-airport site with one passenger. The passenger stated that the last thing that he remembered was the airplane being about 200 feet in the air. The wreckage came to rest at the base of a large berm adjacent to the takeoff site. An on-scene examination of the wreckage revealed no evidence of any preaccident mechanical deficiencies. Ground impact scars and the damage to the airplane were consistent with a high-energy impact, indicative of an aerodynamic stall. Given the lack of mechanical deficiencies with the airplane and engine, and the nature of the damage to the airplane, it is likely that the pilot inadvertently stalled the airplane at a low altitude and was unable to recover.
Probable cause
The pilot did not maintain adequate airspeed during takeoff, which resulted in an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC11FA055
- Event ID
- 20110627X44652
- Case number
- ANC11FA055
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2011-06-27.
- API snapshot SHA-256: ef1b4d4029ec9da509cd561bc3e1a6e14260d91182b966c5ea4c7bfd622e18d5; retrieved 2026-09-13T21:29:03.539Z.