FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12CA254 · Cessna Aircraft Co 162

9 Jun 2012 · Santa Ana, CA, United States

Orange County Flight Center Cessna Aircraft Co 162 · Accident: collision during takeoff/landing during initial climb

From John Wayne Orange County International Airport (SNA) to John Wayne Orange County International Airport (SNA)

Report a problem

Event

NTSB case
WPR12CA254
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 Aircraft Co 162

Aircraft type
Cessna 162
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
N5211Y
Onboard fatalities
Unknown
Route
From John Wayne Orange County International Airport (SNA), Santa Ana, CATo John Wayne Orange County International Airport (SNA), Santa Ana, 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
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
Collision during takeoff/landing
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that just prior to touchdown the airplane encountered a gust of wind, which forced the airplane off of the runway heading. The pilot applied power to go around; however, during the transition to climb, the airplane collided with a taxiway sign, sustaining substantial damage to the side of the fuselage. The pilot continued the climb and returned to land without further incident. No preimpact mechanical malfunctions or failures were reported with the airplane that would have precluded normal operation.

Probable cause

The pilot’s failure to compensate for the gusting wind and failure to maintain airplane control during the approach to land.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12CA254
Event ID
20120609X71211
Case number
WPR12CA254
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: 275b1e05d64f1a15dad5fcb651b3e42d2449d794caef9bc585e3a0f84417eb14; retrieved 2026-09-15T18:26:55.140Z.