# Accident 20231120018779A: Cessna 172N, Blairstown, NJ, November 20, 2023

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 20, 2023, 10:17 local time
- Place: Blairstown, NJ
- Airport: Blairstown
- Damage: Substantial damage
- Phase of flight: Landing: Approach
- Operating rules: Pilot school (Part 141)
- Operator: NUCS
- Location: 40.9711° N, 74.9975° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.9711&lon=-74.9975&mi=10
- Aircraft: N739MK, registered now (https://openairdocs.org/aircraft/N739MK) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor, private pilot, student
- Pilot flight hours: 347 total, 347 in this make and model, 106 in the last 90 days
- NTSB investigation: [NTSB ERA24LA048](https://openairdocs.org/ntsb/ERA24LA048) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20231120018779A

## Narrative

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

THE PILOTS FAILED GO-AROUND ATTEMPT RESULTED IN THE AIRPLANE BANKING TO THE LEFT AND STRIKING THE RUNWAY WHICH SUBSEQUENTLY LED TO THE ACCIDENT. THE PILOT SUBMITTED THE FOLLOWING STATEMENT: “WHILE ON AN INSTRUCTIONAL DUAL FLIGHT WITH A STUDENT PILOT, THE STUDENT WAS PERFORMING A SIMULATED ENGINE OUT LANDING AT BLAIRSTOWN AIRPORT (1N7) TO RUNWAY 7. ONCE OVER THE RUNWAY, I INSTRUCTED THE STUDENT TO PERFORM A GO-AROUND DUE TO EXCESSIVE FLOATING DOWN THE RUNWAY. THE STUDENT ADDED FULL POWER AND PULLED BACK ON THE CONTROLS TO INITIATE THE GO-AROUND. ALMOST IMMEDIATELY AFTER, THE PLANE BANKED TO THE LEFT OF THE RUNWAY. I IMMEDIATELY TOOK OVER THE CONTROLS AND ATTEMPTED TO RECOVER FROM THE SITUATION. UNFORTUNATELY, I WAS UNABLE TO OVERPOWER THE STUDENTS' EXCESSIVE INPUT AND THE AIRPLANE DID NOT RESPOND TO MY ATTEMPT TO RECOVER. THE SEQUENCE OF EVENTS OCCURRED VERY RAPIDLY, AND I HAD MINIMAL TIME TO REACT.”

## 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 ERA24LA048](https://openairdocs.org/ntsb/ERA24LA048), Nov 20, 2023: Cessna 172N (N739MK), Blairstown, NJ, substantial damage. Probable cause: The student pilot’s improper control inputs and the flight instructor’s delayed remedial action, which resulted in a loss of control during an attempted go-around.

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.