FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11LA195 · Cessna 150L

12 Apr 2011 · Corona, CA, United States

Cessna 150L · Accident: loss of control in flight during landing

From Corona Municipal Airport (AJO) to Corona Municipal Airport (AJO)

Report a problem

Event

NTSB case
WPR11LA195
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
N11630
Operator
Fly Corona
Onboard fatalities
Unknown
Route
From Corona Municipal Airport (AJO), Corona, CATo Corona Municipal Airport (AJO), Corona, 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
Landing · flare/touchdown
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that he was practicing a touch-and-go landing and that he pulled up the controls during the landing flare because the airplane was high. He then realized that the airplane was about to stall and added power. The airplane turned left about 45 degrees, bounced once in the adjacent grass, and crossed a taxiway. The airplane subsequently impacted a hangar and the airplane’s engine section to the firewall went through the closed hangar door. Both wings and the cabin area of the fuselage were badly bent and wrinkled. Postaccident examination of the engine, airframe, and flight controls revealed no deficiencies that would have precluded normal operation.

Probable cause

The pilot’s loss of airplane control during the landing flare.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11LA195
Event ID
20110412X41933
Case number
WPR11LA195
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: 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: 5ae6a31a419934e303d451b7feca7d6270dab8d288bc531122807610ce106ba5; retrieved 2026-09-15T16:03:00.568Z.