FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA08LA142 · Cessna 172M

28 May 2008 · Big Bear City, CA, United States

Cessna 172M · Accident: windshear or thunderstorm during landing

From Zamperini Field (TOA) to Big Bear City Airport (L35)

Report a problem

Event

NTSB case
SEA08LA142
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 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
N21134
Operator
Unknown
Onboard fatalities
Unknown
Route
From Zamperini Field (TOA), Torrance, CATo Big Bear City Airport (L35), Big Bear City, 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
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
Windshear or thunderstorm
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
Wire
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

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 was on approach to runway 26 about 80 feet over the runway, when she believed she experienced a severe windshear, which caused the airplane to veer to the left. The pilot raised the flaps, added full power, and initiated a go-around, but was initially unable to get the airplane to climb. A pilot witness reported observing the airplane about 50 feet over the runway, slowing but not descending, and thought it was going to stall. The witness stated that the airplane slowed even more, then banked left and right at up to a 45-degree angle of bank. The witness saw the airplane's wings continue to oscillate in roll, then it banked sharply to the left as the nose achieved a steep nose up attitude, while remaining at 40 to 50 feet above the ground. The airplane then impacted a set of power lines. Wind gusts at the time of the accident were reported at 12 knots. There were no anomalies reported with the airplane prior to the flight. The density altitude at the mountain airport was calculated to be about 7,700 feet.

Probable cause

The pilot's failure to maintain adequate airspeed while on approach to landing that resulted in a stall/mush. Contributing to the accident was the wind shear and the high density altitude condition.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08LA142
Event ID
20080604X00791
Case number
SEA08LA142
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, 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: a2969a33c70f288693d876864e078404c8180d5cdfe8e1902f6391bba93b621b; retrieved 2026-09-15T09:43:48.758Z.