GAA19CA498 · Cessna 172 S
Embry-Riddle Aeronautical University Cessna 172 S and Embry-Riddle Aeronautical University Cessna 172 S · Accident: ground collision while taxiing
Event
- NTSB case
- GAA19CA498
- 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 · 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
- N408ER
- Onboard fatalities
- Unknown
- Route
- From Daytona Beach International Airport (DAB), Daytona Beach, FLTo Daytona Beach International Airport (DAB), Daytona Beach, FL
- Aircraft age
- About 5 years (built 2014)
- 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
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
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
- N465ER
- Onboard fatalities
- Unknown
- Route
- From Daytona Beach International Airport (DAB), Daytona Beach, FLTo Daytona Beach International Airport (DAB), Daytona Beach, FL
- Aircraft age
- About 4 years (built 2015)
- 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
- 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 › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the landing pilot, she landed the airplane and expedited her exit from the runway via Sierra 1 for taxiway Sierra. She had been cleared by the air traffic tower controller to cross runway 16 and proceed to the run-up area for departure from runway 25. Once established on taxiway Sierra, she entered the intersection at taxiway Echo. Subsequently, the airplane was struck from the left by another airplane that had entered the intersection via taxiway Echo. The other pilot reported that he was communicating with a ground controller and that he entered the intersection via taxiway Echo and then turned left onto taxiway Sierra. He reported that he had "double checked" to his left and right before entering the intersection but that his airplane's propeller struck another airplane's left wing. According to air traffic control recordings, a ground controller contacted the pilot of the airplane taxiing on taxiway Echo for taxiway Sierra and asked, "Do you have the traffic off to your right side?" The next two ground transmissions were stepped on, and the airplane entered the intersection and impacted the airplane already established on taxiway Sierra. The airplane established on taxiway Sierra sustained substantial damage to the left wing. Both pilots reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The other pilot's failure to see and avoid the airplane established on the taxiway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA498
- Event ID
- 20190818X24815
- Case number
- GAA19CA498
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2019-08-18.
- API snapshot SHA-256: 8f942fdffc63b0bbc6a7aa79cd08d20c45af37396e7183305cd7c293a3ab7fcd; retrieved 2026-09-13T18:33:26.768Z.