GAA17CA189 · Piper PA 28 181
Bird Acquisition Piper PA 28 181 · Accident: collision during takeoff/landing
From Chandler Municipal Airport (CHD) to Gila Bend Municipal Airport (E63)
Event
- NTSB case
- GAA17CA189
- 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
Piper PA 28 181
- Aircraft type
- Piper PA-28
- 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
- N288PA
- Operator
- Bird Acquisition
- Onboard fatalities
- Unknown
- Route
- From Chandler Municipal Airport (CHD), Chandler, AZTo Gila Bend Municipal Airport (E63), Gila Bend, AZ
- Aircraft age
- About 15 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
- Takeoff
- 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
- Collision during takeoff/landing
- 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 › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that he and two student pilots were on a night, visual flight rules, instructional flight. The instructor tried to activate the pilot-controlled lighting at the destination airport, but he believed that it was inoperative. He reported that he could see the wind sock on the airfield but that he did not see the "X" near the runway numbers and performed a touch and go. During rotation the instructor reported that, "I heard a red cone make impact with the nose gear section." He had to apply continuous forward pressure to the yoke because the nose continued to pitch up with the trim set to the full-down position. He asserted that the flight characteristics were "acceptable" and continued the flight about 47 nautical miles to their home airport. Upon arrival, the instructor alerted the tower that he had a stabilator malfunction and landed the airplane with zero flaps. The instructor reported that he did not check the notices to airmen (NOTAM). The airplane sustained substantial damage to the stabilator.
The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
According to Federal Aviation Administration NOTAM 03/058, the airport runways were closed at the time of the accident.
Probable cause
The flight instructor’s failure to review the notices to airmen related to the airport, which resulted in his landing on a closed runway and the airplane striking runway closed markers.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA189
- Event ID
- 20170316X84435
- Case number
- GAA17CA189
- 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 2017-03-12.
- API snapshot SHA-256: 8e4549da304a3afc25aaf40249fda139e9466ee1d9d0b26c52713ccb1bb92176; retrieved 2026-09-16T05:06:01.010Z.