# Incident 20200523008489I: Piper Aircraft Inc PA-44-180, New Smyrna, FL, May 23, 2020

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 23, 2020, 10:35 local time
- Place: New Smyrna, FL
- Airport: New Smyrna Beach Municipal
- Damage: Minor damage
- Phase of flight: Other, Specify
- Operating rules: Pilot school (Part 141)
- Location: 29.0557° N, 80.9489° W: Placed by OpenAirDocs at NEW SMYRNA BEACH MUNI (JACK BOLT FLD) (EVB), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=29.0557&lon=-80.9489&mi=10
- Aircraft: N417EP, registered now (https://openairdocs.org/aircraft/N417EP) (OpenAirDocs)
- Registry model: Piper PA-44-180 (registry code 7104406, https://openairdocs.org/model/piper-pa-44-180) (OpenAirDocs)
- Registry engine: Lycoming O-360-A1H6 (registry code 42399, https://openairdocs.org/engine/lycoming-o-360-a1h6) (OpenAirDocs)
- Reported make and model: PIPER AIRCRAFT INC PA-44-180
- Reported engine: LYCOMING O-360-A1H6
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- Pilot flight hours: 1,643 total, 690 in this make and model, 339 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20200523008489I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON MAY 23, 2020 IP ^PRIVACY DATA OMITTED^ WAS PRACTICING ABORTED TAKE-OFFS IN A PA-44 WITH HIS STUDENT ON A CLOSED RUNWAY WITH TOWER PERMISSION. IP AND STUDENT BRIEFED WHAT TO DO IF THERE WAS AN ENGINE FAILURE AND HOW TO REACT. IP STATED THE STUDENT INITIATED A SIMULATED TAKEOFF, AND ALMOST IMMEDIATELY THE IP PULLED THE RIGHT ENGINE MIXTURE BACK TO SIMULATE A ROUGH RUNNING ENGINE.  IP SAID THEY HELD THEIR LEFT FOOT OVER THE LEFT RUDDER TO BLOCK IT IN CASE THE STUDENT PUSHED IN THE INCORRECT RUDDER.  IP BEGAN TALKING TO THE STUDENT AS TO WHAT THEY SHOULD DO TO ABORT THE TAKEOFF.  WHEN IT BECAME APPARENT THAT THE STUDENT WAS NOT REACTING, IP CALLED FOR THE CONTROLS AND CLOSED THE THROTTLE AND BEGAN TURNING BACK TOWARDS THE CENTER LINE WITH A COMBINATION OF RUDDER AND BRAKE.  THE AIRPLANE WAS TURNED A BIT TOO FAR TO THE RIGHT, SO WHEN TURNING BACK TOWARDS THE RUNWAY, THE TURN RADIUS OF THE AIRPLANE BROUGHT THE RIGHT PROPELLER OVER ONE OF THE RUNWAY EDGE LIGHTS.  THE RUNWAY EDGE LIGHT BULB WAS SHATTERED ON IMPACT.  IP IMMEDIATELY TAXIED BACK TO THE RAMP TO HAVE MAINTENANCE INSPECT THE AIRPLANE.  AFTER SECURING THE AIRPLANE, IT WAS APPARENT THAT ONE OF THE PROPELLER BLADES WAS DAMAGED ON IMPACT.  IP CALLED THE TOWER TO INFORM THEM OF THE DAMAGE TO THE RUNWAY LIGHT SO THEY COULD INSPECT THE LIGHT AND CLEAN ANY DEBRIS THAT MAY HAVE BEEN LEFT IN THE RUNWAY ENVIRONMENT.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

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