WPR12CA003 · Cessna 172P
Trend Vector Aviation Int Cessna 172P · Accident: propeller/jet/rotor blast or suction while taxiing
From Antonio B. Won Pat International Airport (PGUM) to Antonio B. Won Pat International Airport (PGUM)
Event
- NTSB case
- WPR12CA003
- 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
- N9853L
- Operator
- Trend Vector Aviation Int
- Onboard fatalities
- Unknown
- Route
- From Antonio B. Won Pat International Airport (PGUM), AganaTo Antonio B. Won Pat International Airport (PGUM), Agana
- 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 · from runway
- 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
- Propeller/jet/rotor blast or suction
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said that he returned to the airport and, after landing, was cleared by an air traffic controller to exit the runway and to proceed to parking, which would require his airplane to cross behind a heavy jet airplane. The pilot reported that he was aware that the heavy jet airplane had been on the taxiway all morning doing periodic engine run-ups. The pilot said that he thought about refusing the clearance but did not. While taxiing across the taxiway behind the jet, a jet blast struck the airplane. The airplane initially slid sideways, then the jet blast picked up the left wing and the right wing struck the ground, which caused substantial damage to the right wing.
Probable cause
The pilot's failure to avoid the jet blast while taxiing and the ground air traffic controller's failure to advise the pilot of the hazard.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12CA003
- Event ID
- 20111005X34605
- Case number
- WPR12CA003
- 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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 9fd18c20830e49881b1221fe27a56b1260128f00afe392bacd725814ba870e39; retrieved 2026-09-15T16:48:39.833Z.