# Incident 19991003039549I: Cessna 172P, Orlando, FL, October 3, 1999

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 3, 1999, 11:08 local time
- Place: Orlando, FL
- Airport: Orlando Sanford Airport
- Phase of flight: Climb
- Operating rules: General operating rules (Part 91)
- Location: 28.7772° N, 81.2349° W: Placed by OpenAirDocs at ORLANDO SANFORD INTL (SFB), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=28.7772&lon=-81.2349&mi=10
- Aircraft: N62405, registered now (https://openairdocs.org/aircraft/N62405) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYC O320D2J
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 1,085 total, 500 in this make and model, 344 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19991003039549I

## Narrative

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

ON TAKE OFF APPROX 1100L IFR TRAINING TO DAB. CLEARED TO 2000 ON 360 HEARING.  BEFORE 2000 CLEARED TO 3000, AT 2200 ENGINE HAD A 100 TO 200 RPM DROP.  SUSPECTED MAG PROB. ADJUSTED MIXTURE, NO IMPROVEMENT.  CONTACTED ORL APPROACH FOR TURN BACK TO SFB.  CLEARED TO SFB.  CLEARED TO 2000, AT THIS TIME A DECREASE IN OIL PRESSURE AND INCREASE IN OIL TEMP.  ADVISED APPROACH OF IMMEDIATE TURN TO SFB.  AT THIS POINT ENGINE SEIZED AND PROP STOPPED.  MADE AN EMEGENCY LANDING IN A FIELD 5 MILES NW OF LAKE MONROE, DEBARY, FL.  FAA INSPECTOR WITTNESSED THE ENGINE TEAR DOWN.  IT REVEALED THAT THE MAIN CRANK SHAFT BROKE AT NUMBER FOUR CYCLINDER CAUSING A CATASTROPHIC FAILURE OF THE ENGINE.  SEE ATTACHED PHOTO'S.

## Other reports on N62405 (4)

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

- [Accident 20220717022409A](https://openairdocs.org/incident/20220717022409A), Jul 17, 2022: Cessna 172P (N62405), Lawrenceville, GA, Substantial damage. On July 17, 2022 at approximately 16:10 local time, [privacy data omitted], a Cessna 172, piloted by a student pilot returning from a solo cross-country…
- [Incident 20100105026749I](https://openairdocs.org/incident/20100105026749I), Jan 5, 2010: Cessna 172P (N62405), Pahokee, FL, Minor damage. Pilot lost control of aircraft during landing rollout. Aircraft went off right side of runway and hit a taxiway sign, causing minor damage to the propeller and…
- [Incident 19850525028389I](https://openairdocs.org/incident/19850525028389I), May 25, 1985: Cessna 172P (N62405), Medina, TX, Minor damage. Landed hard due to gusty wind and nose gear collapsed. Insructional flight.
- [Accident 19820901070222A](https://openairdocs.org/incident/19820901070222A), Sep 1, 1982: Cessna 172P (N62405), Plainview, TX, Substantial damage. Overtaken and struck by N520T, after left turn to final. 520T made right to final. Both wrong radio frequency.

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.