# Accident 20011106031009A: Piper PA28161, New Ulm, MN, November 6, 2001

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 6, 2001, 14:45 local time
- Place: New Ulm, MN
- Airport: New Ulm Municipal Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 44.3109° N, 94.4598° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=44.3109&lon=-94.4598&mi=10
- Aircraft: N523PU, registered now (https://openairdocs.org/aircraft/N523PU) (OpenAirDocs)
- Registry model: Piper PA-28-161 (registry code 7102803, https://openairdocs.org/model/piper-pa-28-161) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA28161
- NTSB investigation: [NTSB CHI02LA031](https://openairdocs.org/ntsb/CHI02LA031) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20011106031009A

## Narrative

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

(-23) SIMULATED ENGINE OUT LANDING INITIATED AT 4,500 MSL. STUDENT POSITIONED AIRCRAFT FOR LANDING ON RUNWAY 22 (A GRASS RUNWAY). INSTRUCTOR DIRECTED STUDENT TO LAND SO AS TO AVOID ASPHALT CROSS RUNWAY--I.E. TO EITHER LAND SO AS TO STOP PRIOR TO ASPHALT RUNWAY, OR BEYOND IT. APPROACH PATH WAS TOO HIGH TO LAND AND STOP PRIOR TO CROSSING ASPHALT RUNWAY, AIRCRAFT TOUCHED DOWN ON 22 PAST CROSS RUNWAY, APPROXIMATELY 1200 FEET OF RUNWAY REMAINING. INSTRUCTOR TOOK CONTROL OF AIRPLANE, APPLIED BRAKES, DETERMINED THAT RUNWAY REMAINING WAS INSUFFICIENT TO STOP, SO ADDED POWER TO GO, THEN DECIDED TO ABORT TAKEOFF AND ATTEMPTED TO STOP. AIRCRAFT STOPPED APPROXIMATELY 300 FEET BEYOND RUNWAY END MARKERS--100 FEET BEYOND THE END OF THE RUNWAY 22 GRASS OVERRUN. (.19) ON NOVEMBER 11, 2001, AT 1445 CENTRAL STANDARD TIME, A PIPER PA-28-161, N523PU, PILOTED BY A CERTIFIED FLIGHT INSTRUCTOR (CFI) AND DUAL STUDENT, WAS SUBSTANTIALLY DAMAGED WHEN ON LANDING IT OVERRAN RUNWAY 22 (2,825 FEET BY 160 FEET, TURF), AT THE NEW ULM MUNICIPAL AIRPORT, NEW ULM, MINNESOTA. THE DUAL STUDENT HELD A PRIVATE PILOT CERTIFICATE. THE INSTRUCTIONAL FLIGHT                                                                     WAS OPERATING IN VISUAL METEOROLOGICAL CONDITIONS AND WAS NOT ON A FLIGHT PLAN. THE FLIGHT WAS CONDUCTED UNDER THE PROVISIONS OF 14 CFR PART 91. THE CFI AND STUDENT WERE NOT INJURED. THE INTENDED LOCAL FLIGHT ORIGINATED FROM THE MANKATO REGIONAL AIRPORT (MKT), MANKATO, MINNESOTA, AT 1400.

## 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 CHI02LA031](https://openairdocs.org/ntsb/CHI02LA031), Nov 6, 2001: Piper PA-28-161 (N523PU), New Ulm, MN, substantial damage. Probable cause: The student and flight instructor not using all of the available runway, the inadequate supervision by the flight instructor and the unsuccessful remedial action by the flight instructor. The student…

## Other reports on N523PU (2)

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

- [Accident 20080824846239A](https://openairdocs.org/incident/20080824846239A), Aug 24, 2008: Piper PA28161 (N523PU), New Ulm, MN, Substantial damage. (-23) Aircraft landed in New Ulm and was taxiing to a parking space. While pulling into the parking space the left main gear went onto the grass area and went…
- [Accident 19940917033869A](https://openairdocs.org/incident/19940917033869A), Sep 17, 1994: Piper PA28161 (N523PU), Lafayette, IN, Substantial damage. First solo bounced landing. Lost control. Bounced off runway into air sideways and crashed. No balked landing dual.

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.
