GAA19CA582 · Diamond DA 40 Undesignat
CAE Oxford Aviation Academy Phoenix Diamond DA 40 Undesignat · Accident: runway excursion during landing
From Falcon Field (FFZ) to Falcon Field (FFZ)
Event
- NTSB case
- GAA19CA582
- 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
Diamond DA 40 Undesignat
- Aircraft type
- Diamond DA-40
- 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
- N4119S
- Onboard fatalities
- Unknown
- Route
- From Falcon Field (FFZ), Mesa, AZTo Falcon Field (FFZ), Mesa, AZ
- Aircraft age
- About 9 years (built 2010)
- 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
- Landing · landing roll
- 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
- Runway excursion
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, he intended to do touch-and-goes in the local traffic pattern. While on the downwind leg, the air traffic controller cleared him to land. During the landing roll, past the halfway point on the runway, he increased the engine power to full to takeoff and told the controller that he was doing a "go-around". The controller immediately instructed him to exit the runway on to the last taxiway so the pilot "cut the entire power", applied brakes and full right rudder, but the airplane skidded, exited the runway and impacted a concrete barrier.
The airplane sustained substantial damage to the forward, lower fuselage.
The flight safety officer reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
The pilot added that he wanted to do touch and goes but did not accurately communicate his intentions to the air traffic controller.
Probable cause
The pilot's decision to abort a go-around with insufficient runway remaining to safely stop the airplane, which resulted in a loss of control, runway excursion and impact with a concrete barrier.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA582
- Event ID
- 20190930X01833
- Case number
- GAA19CA582
- 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 2019-09-28.
- API snapshot SHA-256: b035e3adfd6040b04783b5daf0b9bb97b77cc54ba8be77706f4b89e89d500b33; retrieved 2026-09-16T10:15:26.865Z.