FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA18CA189 · Diamond Aircraft IND Inc DA 40 UNDESIGNAT

30 Mar 2018 · Gila Bend, AZ, United States

CAE Oxford Aviation Academy Phoenix Diamond Aircraft IND Inc DA 40 UNDESIGNAT · Accident while taxiing

From Falcon Field (FFZ) to Gila Bend Municipal Airport (E63)

Report a problem

Event

NTSB case
GAA18CA189
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 Aircraft IND Inc 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
N53SL
Onboard fatalities
Unknown
Route
From Falcon Field (FFZ), Mesa, AZTo Gila Bend Municipal Airport (E63), Gila Bend, AZ
Aircraft age
About 13 years (built 2005)
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
Miscellaneous/other
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Pole
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 systems

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that, after taxiing to the ramp, he set the parking brake. He added that he released the foot brake, the airplane rolled forward, and impacted a pole.

The airplane sustained substantial damage to the right wing.

The flight safety officer reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. He added that, after the accident, he verified proper operation of the parking brake.

Probable cause

The pilot’s failure to properly set the parking brake, which resulted in an impact with a pole.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA189
Event ID
20180330X34903
Case number
GAA18CA189
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: 5f53f1ee883c27cdb98f16417404ac9cb760d0c8f3982f6a7274948a507c3f79; retrieved 2026-09-16T06:45:12.546Z.