# Incident 20051111032449I: Cessna 172S, Church Hill, MD, November 11, 2005

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 11, 2005, 15:00 local time
- Place: Church Hill, MD
- Phase of flight: Sfl Cruise
- Operating rules: General operating rules (Part 91)
- Operator: BVQS
- Location: 39.1450° N, 75.9808° W: Placed by OpenAirDocs: center of Church Hill, MD, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.1450&lon=-75.9808&mi=10
- Aircraft: N3501J, a cancelled registration (https://openairdocs.org/deregistered/N3501J-2006-05-10) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 872 total, 112 in this make and model, 51 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20051111032449I

## Narrative

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

(-23) FLIGHT INSTRUCTOR WAS SIMULATING A FORCED LANDING. AFTER THE STUDENT HAD COMPLETED THE PROCEDURES OF THE FORCED LANDING, THE AIRCRAFT WAS AT AN ALTITUDE OF ABOUT 1000'. THE INSTRUCTOR SAID TO ADD POWER, BUT THE AIRCRAFT DID NOT RESPOND. THE FLIGHT INSTRUCTOR TOOK THE CONTROLS AND LANDED THE AIRCRAFT IN A LARGE FIELD WITHOUT ANY DAMAGE TO THE AIRCRAFT. INVESTIGATION FOUND THE THROTTLE LINKAGE WAS NOT INSTALLED CORRECTLY. THE LAST 100 HR INSPECTION WAS PERFORMED BY ^PRIVACY DATA OMITTED^ .

## Other reports on N3501J (1)

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

- [Incident 20020406013349I](https://openairdocs.org/incident/20020406013349I), Apr 6, 2002: Cessna 172S (N3501J), Cambridge, MD, Minor damage. (-23) Pilot and passenger left mtn for a flight to cge. Flight was normal and he entered pattern at cge. Pilot said wind was right down the runway as he flew…

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.