# NTSB GAA19CA498: Cessna 172, N408ER, Daytona Beach, FL, August 18, 2019

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: August 17, 2019, 21:39 local (Aug 18, 2019, 01:39 UTC)
- Place: Daytona Beach, FL
- Coordinates: 29.18, -81.058052 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=29.1800&lon=-81.0581&mi=10
- Phase of flight: [Taxi](https://openairdocs.org/ntsb-phases/250) (OpenAirDocs' grouping)
- Defining events: [Taxi: Ground collision](https://openairdocs.org/ntsb-events/200); [Taxi: Ground collision](https://openairdocs.org/ntsb-events/200)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report July 27, 2020
- Report: Approved by Office Director
- NTSB office: General Aviation Accidents
- Parties: FAA
- NTSB case key (mKey): 100096
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA19CA498
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/100096/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=100096
- Page: https://openairdocs.org/ntsb/GAA19CA498

## Probable cause (aircraft 2)

The pilot entering the taxiway's failure to see and avoid the airplane established on the taxiway

## Probable cause (aircraft 1)

The other pilot's failure to see and avoid the airplane established on the taxiway.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot (probable cause), aircraft 1; cases with it: [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md)
- [Object/animal/substance: aircraft](https://openairdocs.org/ntsb-findings/03022040): Environmental issues › Physical environment · Effect on operation (probable cause), aircraft 1; cases with it: [All aircraft, 116 cases](https://openairdocs.org/ntsb-findings/03022040/cases.md)
- [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot of other aircraft (probable cause), aircraft 2; cases with it: [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md)
- [Object/animal/substance: aircraft](https://openairdocs.org/ntsb-findings/03022040): Environmental issues › Physical environment · Effect on operation (probable cause), aircraft 2; cases with it: [All aircraft, 116 cases](https://openairdocs.org/ntsb-findings/03022040/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Taxi: Ground collision](https://openairdocs.org/ntsb-events/200) (defining event), aircraft 1; cases with it: [All aircraft, 618 cases](https://openairdocs.org/ntsb-events/200/sequence.md)
- [Taxi: Ground collision](https://openairdocs.org/ntsb-events/200) (defining event), aircraft 2; cases with it: [All aircraft, 618 cases](https://openairdocs.org/ntsb-events/200/sequence.md)

## Analysis (aircraft 2)

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.

## Analysis (aircraft 1)

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.

## Factual narrative (aircraft 2)

According to the landing pilot, she landed, and expedited her exit from the runway via Sierra 1 for taxiway Sierra. She had been cleared by tower to cross runway 16 and to proceed to the runup area for another departure from runway 25. Established on taxiway Sierra, she entered the intersection at taxiway Echo and the airplane was struck from the left by an airplane that entered the intersection via taxiway Echo. The pilot that entered the intersection via taxiway Echo was communicating with ground and continued into the intersection and made a left turn onto taxiway Sierra. He reported that he had, "double checked" to his left and his right, prior to entering the intersection, but his airplane's propeller struck the left wing of another airplane. According to ATC recordings, ground contacted the airplane taxing 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 collided with 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.

## Factual narrative (aircraft 1)

According to the landing pilot, she landed, and expedited her exit from the runway via Sierra 1 for taxiway Sierra. She had been cleared by tower to cross runway 16 and to proceed to the runup area for another departure from runway 25. Established on taxiway Sierra, she entered the intersection at taxiway Echo and the airplane was struck from the left by an airplane that entered the intersection via taxiway Echo. The pilot that entered the intersection via taxiway Echo was communicating with ground and continued into the intersection and made a left turn onto taxiway Sierra. He reported that he had, "double checked" to his left and his right, prior to entering the intersection, but his airplane's propeller struck the left wing of another airplane. According to ATC recordings, ground contacted the airplane taxing 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 collided with 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.

## Aircraft 1

- Registration: N408ER (not matched to a registry record)
- Reported make and model: Cessna 172 (S)
- Category: Airplane
- Serial number: 172S11439
- Year built: 2014
- Airframe hours: 5276.5
- Engines: Lycoming IO-360-L2A 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Operator: Embry Riddle Aeronautical University Inc
- Registered owner: Embry Riddle Aeronautical University Inc
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, July 30, 2019
- Departed: DAB, Daytona Beach, FL
- Destination: DAB, Daytona Beach, FL
- Airport: DAB, Daytona Beach Intl
- Equipment: Electronic primary flight display, Onboard weather, Stall warning system, Electronic multifunction display, ADS-B, Auto-pilot

## Aircraft 2

- Registration: N465ER (not matched to a registry record)
- Reported make and model: Cessna 172 (S)
- Category: Airplane
- Serial number: 172S11606
- Year built: 2015
- Airframe hours: 4049.6
- Engines: Lycoming IO-360-L2A 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Operator: Embry-Riddle Aeronautical University Inc
- Registered owner: Embry-Riddle Aeronautical University Inc
- Airworthiness certificate: Standard, Normal
- Last inspection: Continuous airworthiness, August 13, 2019
- Departed: DAB, Daytona Beach, FL
- Destination: DAB, Daytona Beach, FL
- Airport: DAB, Daytona Beach Intl
- Equipment: Electronic primary flight display, Electronic multifunction display, Auto-pilot, ADS-B, Stall warning system, Onboard weather

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot, aircraft N408ER; age 22; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review May 7, 2019; seat: left; flight hours: 231 total, 231 in this make and model, 66 as pilot in command, 18 in the last 90 days, 8 in the last 30 days
- Pilot, aircraft N465ER; age 22; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review July 20, 2019; seat: left; flight hours: 117 total, 117 in this make and model, 47 as pilot in command, 40 in the last 90 days, 11 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 220° at 14 knots
- Visibility: 10 statute miles
- Lowest ceiling: 15,000 ft broken
- Observed at: KDAB, 1 nm away

## FAA reports on this event (2)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20190817016352A](https://openairdocs.org/incident/20190817016352A), Aug 17, 2019: Cessna 172S, Daytona Beach, FL, Substantial damage. On August 17, 2019 N408ER a CE-172 was conducting touch and goes at night at Daytona Beach international airport. During this practice and after landing the…
- [Accident 20190817016362A](https://openairdocs.org/incident/20190817016362A), Aug 17, 2019: Cessna 172S, Daytona Beach, FL, Substantial damage. On August 17, 2019 at Daytona Beach international airport kdab the airman taxied from the erau ramp to runway 25L for night touch and goes. The airman followed…

## Docket (4 files)

The files NTSB released with the investigation on January 17, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=100096. 7.1 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1_N408ER (item 1, .PDF, 3.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40480025&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1_N408ER-Master.PDF
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1_N465ER (item 2, .PDF, 3.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40480026&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1_N465ER-Master.PDF
- Air Traffic Control (item 3, .PDF, 36 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40480027&FileExtension=.PDF&FileName=Air%20Traffic%20Control-Master.PDF
- Photo (item 4, .PDF, 137 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40480028&FileExtension=.PDF&FileName=Photo-Master.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
