FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12CA260 · Cessna 172P

28 May 2012 · Hemet, CA, United States

Cessna 172P · Accident: ground collision while taxiing

From Montgomery-Gibbs Executive Airport (KMYF) to Hemet Ryan Airport (KHMT)

Report a problem

Event

NTSB case
WPR12CA260
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 172P

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
N216AF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Montgomery-Gibbs Executive Airport (KMYF), San Diego, CATo Hemet Ryan Airport (KHMT), Hemet, 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
Taxi
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
Ground collision
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
Pole
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

  • Personnel issues › Psychological

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

NTSB narrative

The student pilot landed the airplane and was taxiing to a fueling facility when he decided that he did not have sufficient time to get fuel and still return the airplane within the allotted rental time. He maneuvered the airplane to a parking area, performed a U-turn, and, while maneuvering the airplane toward the taxiway center line, he saw a lamp post to his left. He immediately applied brake and rudder control input, but the airplane skidded, and the left wing struck the pole. The left aft wing spar sustained substantial damage during the impact sequence. The pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation.

Probable cause

The student pilot's failure to monitor and maintain clearance from an obstacle during taxi.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12CA260
Event ID
20120614X20148
Case number
WPR12CA260
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: d1848120d58df4e984bff7ad0cd66270adb4219c97e8d35617a8fef475dbcc2b; retrieved 2026-09-15T18:29:59.274Z.