# NTSB SEA08LA069: Piper PA-32R-301T, N73BL, Parowan, UT, February 4, 2008

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: February 4, 2008, 11:30 local (18:30 UTC)
- Place: Parowan, UT
- Coordinates: 37.859722, -112.816108
- Nearby events: https://openairdocs.org/map.md?lat=37.8597&lon=-112.8161&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report May 28, 2008
- Report: Approved by Office Director
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 67468
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA08LA069
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/67468/pdf
- Page: https://openairdocs.org/ntsb/SEA08LA069

## Probable cause

The pilot's improper in-flight decision not to over fly/inspect the snow covered runway prior to landing, and his failure to align the airplane over the centerline of the runway. Contributing to the accident was the snow covered runway, the airport operator's failure to properly plow and clear the runway, and hidden obstructions (previously plowed snow) under the freshly fallen snow.

## Findings

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

- [Runway/land/takeoff/taxi surface: snow/slush/ice covered surface](https://openairdocs.org/ntsb-findings/03023015): Environmental issues › Physical environment · Not specified (probable cause); cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/03023015/cases.md?model=7103220), [All aircraft, 219 cases](https://openairdocs.org/ntsb-findings/03023015/cases.md)
- [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-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/03022052/cases.md?model=7103220), [All aircraft, 36 cases](https://openairdocs.org/ntsb-findings/03022052/cases.md)
- [Action: incomplete action](https://openairdocs.org/ntsb-findings/02041040): Personnel issues › Action/decision · Airport personnel (probable cause); cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/02041040/cases.md?model=7103220), [All aircraft, 105 cases](https://openairdocs.org/ntsb-findings/02041040/cases.md)
- [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-32R-301T, 8 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7103220), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md)
- [Landing gear system](https://openairdocs.org/ntsb-findings/01023200): Aircraft › Aircraft systems · Capability exceeded; cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/01023200/cases.md?model=7103220), [All aircraft, 113 cases](https://openairdocs.org/ntsb-findings/01023200/cases.md)
- [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-32R-301T, 3 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=7103220), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md)

## Sequence of events

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

- [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) (defining event); cases with it: [Piper PA-32R-301T, 19 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103220), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)
- [Landing-landing roll: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Piper PA-32R-301T, 3 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=7103220), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md)

## Analysis

During a landing on a runway covered by about two to three inches of freshly fallen snow, one of the airplane's main landing gear impacted a snow covered mound of previously plowed snow that had hardened. That impact threw the airplane sideways, whereupon it collided with more of the previously plowed and hardened snow, resulting in the collapse of all the landing gear struts. The investigation determined that the last time that the runway was plowed, the snow had not been cleared all the way to the edge of the runway's paved surface, and there was therefore piles of previously plowed snow on the outer portions of the runway surface. Some of that snow was located 10 to 12 feet inboard of the edge of the runway surface. When the new snow fell, it became very hard to distinguish between the area where the previously cleared surface was covered only by the newly fallen snow, and the area where the chunks of previously plowed snow had piled up, hardened, and then been covered by the new snow. The pilot departed the same airport two days before the accident, and had seen the condition of the partially plowed runway. When he returned for landing on the day of the accident, he assumed that the old snow had been cleared away prior to the new snow falling, and that the entire runway was then covered only with the two to three inches of freshly fallen snow. Because he made that assumption, the pilot did not take advantage of the opportunity to perform a low approach and inspect the entire runway surface prior to landing. Soon after the airplane touched down, the pilot realized that the previously plowed snow was still on the edges of the runway, and that he had not touched down on the centerline. The pilot saw the chunks of snow-covered old snow prior to the impact, but before he could take remedial action, one of the airplane's main gear collided with a chunk of hardened old snow, and the accident sequence was initiated.

## Factual narrative

On February 4, 2008, about 1130 mountain standard time, a Piper PA-32R-301T, N73BL, collided with hardened chunks of previously plowed snow during the landing roll at Parowan Airport, Parowan, Utah. The airline transport pilot, who was the sole occupant of the airplane, was not injured, but the airplane, which is owned and operated by the pilot, sustained substantial damage. The 14 CFR Part 91 personal transportation flight, which departed Las Vegas, Nevada, about 0900 Pacific standard time, was being operated in visual meteorological conditions. The pilot had originally been on an Instrument Flight Rules (IFR) flight plan, but had canceled his IFR clearance once he had the airport in sight. There was no report of an ELT activation.

According to the pilot, he had landed at the Parowan Airport many times over a number of years, but on the day of the accident the runway was covered with two or three inches of new snow. Because of the snow coverage, he could not easily tell where the centerline of the runway was, and after the airplane touched down, one of its main landing gear impacted a snow covered mound of previously plowed snow. That impact threw the airplane sideways, whereupon it collided with more of the previously plowed snow. During this sequence, all three landing gear struts collapsed, and the underside of the airplane's belly sustained considerable structural damage.

During the investigation it was determined that the last time that the runway was plowed by the Parowan Public Works Department, the snow had not been cleared all the way to the edge of the runway's paved surface. Instead, only about a 50 foot wide swath was cleared on the 75 foot wide surface. Therefore, when the new snow fell, it became very hard to distinguish between the area where the previously cleared surface was covered only by the newly fallen snow, and the area where the chunks of previously plowed snow had piled up, hardened, and then been covered by the new snow.

In a telephone conversation with the NTSB Investigator-In-charge (IIC), the pilot stated that when he departed Parowan two days prior to the accident, there was no snow on the center portion of the runway (approximately a 50 foot wide irregularly cut swath), but that the old previously plowed snow was piled along both sides of the entire length of the runway. He estimated that at that time the piles of old snow extended onto both sides of the runway surface about 10 to 12 feet from its edge. He further stated that fresh snow had fallen while he was gone from the area, and as he lined up for his final approach on the day of the accident, everything appeared white and flat. He therefore assumed that the old snow had been cleared away prior to the new snow falling, and that the entire runway was covered only with the two to three inches of freshly fallen snow.

Because the pilot made that assumption, he did not take advantage of the opportunity to inspect the runway during a low approach prior to landing. Soon after the airplane touched down, the pilot realized that the previously plowed snow was still on the edges of the runway, and that he had not touched down on the centerline. According to the pilot, he saw the chunks of snow covered old snow prior to the impact, but before he could take remedial action, one of the airplane's main gear collided with a chunk of hardened old snow, and the accident sequence was initiated.

## Aircraft

- Registration: [N73BL](https://openairdocs.org/aircraft/N73BL), registered now, S/N 3257450 (OpenAirDocs)
- Reported make and model: Piper PA-32R-301T
- Registry model: [Piper PA-32R-301T](https://openairdocs.org/model/piper-pa-32r-301t) (registry code 7103221) (OpenAirDocs)
- Category: Airplane
- Serial number: 3257450
- Airframe hours: 235
- Engines: Lycoming TIO-540-AH1A 300 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Battista A. Locatelli
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, April 1, 2007
- Departed: KVGT, Las Vegas, NV
- Destination: 1L9, Parowan, UT
- Flight plan: IFR
- Airport: 1L9, Parowan Airport, runway 22, 5,000 × 75 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 76; injuries: none; airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review April 1, 2007; seat: left; flight hours: 6,339 total, 561 in this make and model, 61 in the last 90 days, 27 in the last 30 days, 2 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 25 °F, dew point 19 °F
- Altimeter: 29.81 inHg

## 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 20080204009719A](https://openairdocs.org/incident/20080204009719A), Feb 4, 2008: Piper PA32R301T, Parowan, UT, Substantial damage. (-23) Pilot landed left of runway 22 at Parowan, UT. Runway had one inch of fresh snow and pilot misjudged where the center line would be. A/c landed with the…

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.