# Incident 20160427008069I: Dassault-Breguet FALCON 20, Ypsilanti, MI, April 27, 2016

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 27, 2016, 22:00 local time
- Place: Ypsilanti, MI
- Airport: Willow Run
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: Air taxi and commuter (Part 135)
- Operator: HAEA
- Location: 42.2403° N, 83.5315° W: Placed by OpenAirDocs at WILLOW RUN (YIP), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=42.2403&lon=-83.5315&mi=10
- Aircraft: N314TW, registered now (https://openairdocs.org/aircraft/N314TW) (OpenAirDocs)
- Registry model: Dassault-Breguet FALCON 20 (registry code 2730103, https://openairdocs.org/model/dassault-breguet-falcon-20) (OpenAirDocs)
- Registry engine: GE CF700 series (registry code 30010, https://openairdocs.org/engine/ge-cf700-series) (OpenAirDocs)
- Reported make and model: DASSAULT-BREGUET FALCON 20
- Reported engine: GE
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport, flight instructor
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160427008069I

## Narrative

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

ON 04/27/2016, N314TW, A FALCON 20 CARGO AIRCRAFT, DECLARED AN EMERGENCY ASSOCIATED WITH A LEFT MAIN GEAR THAT DID NOT EXTEND.  THE AIRCRAFT LANDED ON RUNWAY 23L AT THE KYIP (WILLOW RUN AIRPORT). ACCORDING TO AN INTERVIEW WITH THE CREWMEMBERS, THE APPROPRIATE QRH PROCEDURE FOR AN EMERGENCY GEAR EXTENSION WAS COMPLETED WITH NO SUCCESS.  THE AIRCRAFT LANDED ON THE CENTERLINE, AND DIRECTIONAL CONTROL WAS MAINTAINED AS LONG AS THE AIRCRAFT WOULD ALLOW.  THE AIRCRAFT SLID INTO THE GRASS TO THE SOUTH SIDE OF RUNWAY 23L.  TWO SOULS WERE ONBOARD AND NO INJURIES RESULTED FROM THIS INCIDENT.  APPROXIMATE FUEL REMAINING ONBOARD AIRCRAFT AT TOUCHDOWN WAS FIFTEEN MINUTES (FUEL RESERVES WERE USED TO ACCOMPLISH EMERGENCY PROCEDURES).  AIRCRAFT WAS INSPECTED ON SCENE, THE LEFT MAIN GEAR WAS STILL IN THE WHEEL WELL.  THE AIRCRAFT WAS BEING REPOSITIONED FOR REVENUE FROM KFLL (FORT LAUDERDALE, FL), NO CARGO ONBOARD.  THE AIRCRAFT WAS REMOVED FROM THE RUNWAY ENVIRONMENT.  IT WAS INSPECTED BY THE OPERATORS' MAINTENANCE PERSONNEL, WHO COORDINATED WITH FAA INVESTIGATORS TO DETERMINE A CAUSE.  MAINTENANCE PERSONNEL DISCOVERED FAILURE OF A GEAR DOOR TELEFORCE SEQUENCING CABLE NOT MOVING, RESULTING IN A LANDING GEAR DOOR SEQUENCE PROBLEM.  THE GEAR BEGAN TO EXTEND, HOWEVER WAS CAUGHT UP ON THE LANDING GEAR DOOR THAT HAD NOT EXTENDED AND WAS JAMMED. THE CABLE WAS REMOVED AND FOUND TO BE SEIZED.  AFTER REVIEW OF MAINTENANCE RECORDS, REQUIRED INSPECTIONS WERE COMPLETED AS REQUIRED BY THE OPERATORS? MAINTENANCE PROGRAM.  THE CAUSE OF THIS INCIDENT WAS A FAILURE OF THE TELEFORCE CONTROL-INTERLINKED PART.  A TRIGGERED PTRS ENTRY (GL23201604123) WAS CREATED BY AN FAA MAINTENANCE INSPECTOR WHO ASSISTED IN THE INVESTIGATION.

NTSB WAS CONTACTED AND DETERMINED THIS WOULD BE CLASSIFIED AS AN INCIDENT DUE TO TYPE OF DAMAGE THAT HAD OCCURRED.

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.