GAA19CA079 · Pilatus PC12 45
Daylight Nightlight Ez Flight Pilatus PC12 45 and Atp Aircraft 4 Cessna 172 S · Accident: ground collision while taxiing
Event
- NTSB case
- GAA19CA079
- 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
Aircraft 1 · Pilatus PC12 45
- Aircraft type
- Pilatus PC12
- 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
- N552TC
- Operator
- Daylight Nightlight Ez Flight
- Onboard fatalities
- Unknown
- Route
- From Mesa Gateway Airport (IWA), Mesa, AZTo Monterey Regional Airport (MRY), Monterey, CA
- Aircraft age
- About 16 years (built 2002)
- 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 · to 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
- Minor
Aircraft 2 · Cessna 172 S
- 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
- N976SP
- Operator
- Atp Aircraft 4
- Onboard fatalities
- Unknown
- Route
- From Mesa Gateway Airport (IWA), Mesa, AZTo Mesa Gateway Airport (IWA), Mesa, AZ
- Aircraft age
- About 19 years (built 1999)
- 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
- 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
- Environmental issues › Physical environment
- Personnel issues › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the Pilatus reported that, after the local air traffic controller gave him an instrument flight rules clearance, he taxied the airplane from the ramp to the taxiway. While turning onto the taxiway, the controller instructed him to give way to an airplane on the same taxiway. He acknowledged the instruction; stopped the airplane; looked left and saw a Cessna, which had already passed him. He then looked right and did not see any other airplanes on the taxiway and continued to taxi. Shortly after, he realized that the airplane's propeller had struck something, so he immediately shut down the engine, deplaned, and realized that he had struck another Cessna that he had not seen.
The flight instructor in the Cessna reported that, while the student pilot was taxiing back to the ramp, they were instructed by the local air traffic controller to follow company traffic while passing another airplane to their left, "holding" short of the same taxiway. He then looked left outside of the window and saw a spinning propeller moving closer toward the airplane. He immediately grabbed the controls and hammered the right pedal, but the other airplane's propeller struck their airplane's left wing.
The Pilatus sustained damage to the propeller. The Cessna sustained substantial damage to the left wing.
The pilot and the flight instructor reported that there were no preaccident mechanical failures or malfunctions with their airplanes that would have precluded normal operation.
A video provided by the airport authority showed that the Pilatus taxied left onto the taxiway from the ramp without stopping and that there was another airplane farther down the taxiway.
Probable cause
The pilot's failure to follow the air traffic controller’s instructions and his subsequent failure to maintain adequate lookout to see and avoid the other airplane on the taxiway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA079
- Event ID
- 20181128X85901
- Case number
- GAA19CA079
- 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: 3327a8777aa3d1acc6dbdced33cf4d72d31ff9cf61580146aaa20be26a5f156c; retrieved 2026-09-13T18:31:42.241Z.