GAA17CA189

NTSB accident investigation · Piper PA 28 · Gila Bend, AZ · March 12, 2017

Accident · No injuriesData collectionFinal report
Date
March 11, 2017, 19:00 local (Mar 12, 2017, 02:00 UTC)
Place
Gila Bend, AZ
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N288PAPiper PA 28
Defining event
Takeoff: Collision during takeoff/land
Weather
Visual (VMC) · Night
Status
Completed · report September 22, 2017
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20170311001319A
Case key
94875

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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.

Findings · 3

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Planning/preparation: flight planning/navigationPersonnel issues › Task performance · Instructor/check pilotPiper PA-28-181: 1 caseAll aircraft: 179 casesProbable cause
Action: incorrect action performancePersonnel issues › Action/decision · Instructor/check pilotPiper PA-28-181: 11 casesAll aircraft: 1,386 casesProbable cause
Object/animal/substance: sign/markerEnvironmental issues › Physical environment · Effect on equipmentPiper PA-28-181: 8 casesAll aircraft: 214 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

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.

Factual 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 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 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 Airman. 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.

Aircraft

Registration
N288PA
Reported as
Piper PA 28 (181)
Category
Airplane
Serial number
2843502
Built
2002
Airframe hours
16,919
Engine
Lycoming O-360-A4M, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Instructional · Part 91
Operator
Bird Acquisition LLC
Registered owner
Bird Acquisition LLC
Airworthiness certificate
Standard, Normal
Last inspection
AAIP · March 9, 2017
Departed
CHD · Chandler, AZ
Destination
E63 · Gila Bend, AZ
Flight plan
VFR
Airport
E63 · Gila Bend Muni, runway 22, 5,200 × 75 ft, asphalt
Equipment
ADS-B, Electronic flight bag or handheld device, Stall warning system

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Flight instructor
Age
25
Injuries
None
Certificates
Flight instructor, Commercial
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 1, Without waivers/limitations
Seat
Front
Restraint
None
Flight hours
390 total · 140 in this make and model · 320 as pilot in command · 130 in the last 90 days · 45 in the last 30 days · 0 in the last 24 hours
Role
Student pilot
Age
24
Injuries
None
Certificate
Student
Medical
Class 3
Seat
Front
Restraint
None
Flight hours
27 total · 27 in this make and model · 27 in the last 90 days · 15 in the last 30 days

Weather

Conditions
Visual (VMC) · Night
Wind
330° at 3 knots
Visibility
9 statute miles
Lowest ceiling
None
Temperature
77 °F, dew point 45 °F
Altimeter
29.92 inHg
Observed at
KBXK, 27 nm away

Docket · 3

The files NTSB released with the investigation on August 29, 2017, on NTSB’s docket system: statements, records, photos and specialists’ reports. 5.2 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.

Other investigations on N288PA · 1

Matched to the same aircraft by N-number and date.