WPR11LA443 · Cessna 152
Cessna 152 · Accident: abnormal runway contact during landing
From Redlands Municipal Airport (REI) to Redlands Municipal Airport (REI)
Event
- NTSB case
- WPR11LA443
- 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 152
- Aircraft type
- Cessna 152
- 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
- N4649L
- Operator
- Accelerated 360
- Onboard fatalities
- Unknown
- Route
- From Redlands Municipal Airport (REI), Redlands, CATo Redlands Municipal Airport (REI), Redlands, CA
- Aircraft age
- About 31 years (built 1980)
- 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
- Abnormal runway contact
- 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 › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that, during a solo training flight, which included an unusual attitude recovery from an aborted landing, he told the student pilot to set up the approach. As the airplane entered the landing flare, the flight instructor pitched the airplane for a higher-than-normal attitude to simulate a balloon effect. Once the airplane started to "slow/stall," the flight instructor told the student pilot to perform a go-around. The student pilot advanced the throttle full forward, but it took "a full second" for the engine to achieve full power, and, by that time, the airplane had stalled and was left of the runway centerline. The flight instructor took the controls and corrected the airplane to the right. The airplane subsequently struck the runway in a left-wing-low attitude, bounced two times, and came to rest adjacent to the runway. A witness to the accident reported that the engine was producing power at the time of the accident.
Probable cause
The flight instructor’s delayed remedial action and failure to maintain airplane control while performing a simulated aborted landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11LA443
- Event ID
- 20110912X83401
- Case number
- WPR11LA443
- 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: 6a6746ce37c363cfd69dea4cda9e0e0ede4d3978e1b0a35a4d4763128c45e815; retrieved 2026-09-15T16:43:58.826Z.