# Incident 20031022029979I: Enstrm F28C, Lapeer, MI, October 22, 2003

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 22, 2003
- Place: Lapeer, MI
- Airport: Dupont-Lapeer Airport
- Phase of flight: Pwr On Vertical Ldng/Rtrcrft
- Operating rules: General operating rules (Part 91)
- Location: 43.0667° N, 83.2722° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=43.0667&lon=-83.2722&mi=10
- Aircraft: N77HX, registered now (https://openairdocs.org/aircraft/N77HX) (OpenAirDocs)
- Registry model: Enstrom F-28C (registry code 3300407, https://openairdocs.org/model/enstrom-f-28c) (OpenAirDocs)
- Registry engine: Lycoming HIO-360 series (registry code 41524, https://openairdocs.org/engine/lycoming-hio-360-series) (OpenAirDocs)
- Reported make and model: ENSTRM F28C
- Reported engine: LYC HIO360E1AD
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 2,960 total, 1,100 in this make and model, 240 in the last 90 days
- NTSB investigation: [NTSB CHI04IA018](https://openairdocs.org/ntsb/CHI04IA018) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20031022029979I

## Narrative

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

(-23) THE TAIL ROTOR PITCH CONTROL CABLE FOR THE RIGHT PEDAL BROKE JUST FORWARD OF THE TAIL ROTOR GEAR BOX.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CHI04IA018](https://openairdocs.org/ntsb/CHI04IA018), Oct 22, 2003: Enstrom F-28C (N77HX), Lapeer, MI, incident, minor damage. Probable cause: Complete failure of the right anti-torque cable while on final approach for landing. A factor was the diminished tail rotor control resulting from the broken cable.

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.
