Mesa Airlines de Havilland DHC-8 202 accident
de Havilland DHC-8 202 · Accident: ground collision while taxiing
From General José María Yáñez International Airport (GYM) to Phoenix Sky Harbor International Airport (PHX)
Event
- NTSB case
- WPR09LA211
- 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
- Airline
- 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
de Havilland DHC-8 202
- Aircraft type
- de Havilland DHC-8
- 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
- N449YV
- Operator
- Mesa Airlines
- Onboard fatalities
- Unknown
- Route
- From General José María Yáñez International Airport (GYM), GuaymasTo Phoenix Sky Harbor International Airport (PHX), Phoenix, AZ
- 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 121: Air Carrier
- 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
- Ground collision
- 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 handling/service
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The captain reported that upon arrival at the ramp area they had to wait for marshalers to arrive so that the airplane could be guided to the gate. As the marshalers were guiding the airplane, the captain lost sight of the ground power unit (GPU) on the right side and queried the first officer several times about whether they were clear of the GPU. The first officer responded that they were clear of the GPU; however, the right engine's propeller blades struck the GPU as the marshaler was crossing his arms to stop movement. The GPU struck the fuselage and damaged the propeller assembly. Federal Aviation Administration inspectors reported that the GPU was not parked in its designated spot and was located about 7 feet aft of its required parking spot.
Probable cause
The failure of ramp personnel and the flight crew to maintain clearance from ground equipment while taxiing. Contributing to the accident was the improper positioning of the ground equipment.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09LA211
- Event ID
- 20090422X95319
- Case number
- WPR09LA211
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2009-04-21.
- API snapshot SHA-256: a084a0e5ccb753d672baa4e58c77dfdfaa7d4646b27fdf57776cd4b14d7cd169; retrieved 2026-09-15T10:58:23.027Z.