# NTSB CHI08CA265: Piper PA-28-161, N523PU, New Ulm, MN, August 24, 2008

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: August 24, 2008, 18:30 local (23:30 UTC)
- Place: New Ulm, MN
- Coordinates: 44.321388, -94.503608
- Nearby events: https://openairdocs.org/map.md?lat=44.3214&lon=-94.5036&mi=10
- Phase of flight: [Taxi](https://openairdocs.org/ntsb-phases/250) (OpenAirDocs' grouping)
- Defining event: [Taxi-from runway: Airport occurrence](https://openairdocs.org/ntsb-events/070)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report September 26, 2008
- Report: Approved by Office Director
- NTSB case key (mKey): 68914
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI08CA265
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/68914/pdf
- Page: https://openairdocs.org/ntsb/CHI08CA265

## Probable cause

The failure of airport personnel to correct a hazardous condition on the airport. A factor was the uncovered manhole.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Object/animal/substance: hidden/submerged object](https://openairdocs.org/ntsb-findings/03022052): Environmental issues › Physical environment · Not specified (probable cause); cases with it: [Piper PA-28-161, 1 case](https://openairdocs.org/ntsb-findings/03022052/cases.md?model=7102803), [All aircraft, 36 cases](https://openairdocs.org/ntsb-findings/03022052/cases.md)
- [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Airport personnel (probable cause); cases with it: [Piper PA-28-161, 8 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=7102803), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Taxi-from runway: Airport occurrence](https://openairdocs.org/ntsb-events/070) (defining event); cases with it: [Piper PA-28-161, 2 cases](https://openairdocs.org/ntsb-events/070/sequence.md?model=7102803), [All aircraft, 56 cases](https://openairdocs.org/ntsb-events/070/sequence.md)
- [Taxi-from runway: Ground collision](https://openairdocs.org/ntsb-events/200); cases with it: [Piper PA-28-161, 13 cases](https://openairdocs.org/ntsb-events/200/sequence.md?model=7102803), [All aircraft, 618 cases](https://openairdocs.org/ntsb-events/200/sequence.md)

## Analysis

The airport manager stated that following the accident, he contacted the company that had been working in the hole, and was told that the cover was too heavy for one person to lift which is why it was not placed back over the hole. The pilot reported that after landing he was taxiing into a tie down spot on the ramp when the left main gear dropped into an open manhole in the grass near the edge of the ramp. He stated that because the tie down spaces are so close to the edge of the ramp, he had to taxi into the grass in order to make the turn into the tie down space. He did not see the hole prior to contacting it, nor was the open hole marked in any way. The airport manager stated the manhole cover was a concrete, 150 pound, 4 foot by 4 foot by 3 inch high lid that covered the hole containing the electrical junction box for the fuel pumps. He stated that the fuel company and a local electric company had worked in the manhole several weeks prior to the accident. He stated he assumed they replaced the cover over the hole when they were finished with the work, but the cover was still on the grass next to the hole. The cover and the hole were not visible from the ramp due to the grass. The airport manager stated that one of the airport line personnel had seen the cover off of the hole, but did not report it to him or anyone else.

## Factual narrative

On August 24, 2008, at 1830 central daylight time, a Piper PA-28-161, N523PU, collided with an open manhole while taxiing after landing at the New Ulm Municipal Airport (ULM), New Ulm, Minnesota. The private pilot and one passenger on board were not injured. The airplane sustained substantial damage to the wings. The personal flight was operating under Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed and no flight plan was filed. The flight originated from the Flying Cloud Airport (FCM), Eden Prairie, Minnesota, at 1740. The pilot reported that after landing he was taxiing into a tie down spot on the ramp when the left main gear dropped into an open manhole in the grass near the edge of the ramp. He stated that because the tie down spaces are so close to the edge of the ramp, he had to taxi into the grass in order to make the turn into the tie down space. He did not see the hole prior to contacting it, nor was the open hole marked in any way. The airport manager stated the manhole cover was a concrete, 150 pound, 4 foot by 4 foot by 3 inch high lid that covered the hole containing the electrical junction box for the fuel pumps. He stated that the fuel company and a local electric company had worked in the manhole several weeks prior to the accident. He stated he assumed they replaced the cover over the hole when they were finished with the work, but the cover was still on the grass next to the hole. The cover and the hole were not visible from the ramp due to the grass. The airport manager stated that one of the airport line personnel had seen the cover off of the hole, but did not report it to him or anyone else. The airport manager stated that following the accident, he contacted the company that had been working in the hole, and was told that the cover was too heavy for one person to lift which is why it was not placed back over the hole.

## Aircraft

- Registration: [N523PU](https://openairdocs.org/aircraft/N523PU), registered now, S/N 2841188, built 1989 (OpenAirDocs)
- Reported make and model: Piper PA-28-161
- Registry model: [Piper PA-28-161](https://openairdocs.org/model/piper-pa-28-161) (registry code 7102803) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 2841188
- Engines: Lycoming O-320 reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Thunderbird Aviation
- Registered owner: Metro Aircraft Co.
- Airworthiness certificate: Standard, Normal
- Departed: FCM, Eden Prairie, MN

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 42; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; flight hours: 151 total, 87 in this make and model, 87 as pilot in command, 8 in the last 90 days, 8 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20080824846239A](https://openairdocs.org/incident/20080824846239A), Aug 24, 2008: Piper PA28161, 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…

## Other investigations on N523PU (2)

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…
- [NTSB CHI94LA335](https://openairdocs.org/ntsb/CHI94LA335), Sep 17, 1994: Piper PA-28-161 (N523PU), W. Lafayette, IN, substantial damage. Probable cause: THE PILOT'S IMPROPER LEVEL-OFF AND RECOVERY FROM A BOUNCED LANDING. A FACTOR IN THE ACCIDENT WAS THE PILOT'S LACK OF TRAINING FOR RECOVERY FROM BOUNCED LANDINGS AND/OR ABORTED TAKEOFFS.

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.

---
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.