DEN04LA045

NTSB accident investigation · Cessna 172N · Parowan, UT · February 13, 2004

Accident · No injuriesLimited investigationFinal report
Date
February 12, 2004, 23:00 local (Feb 13, 2004, 06:00 UTC)
Place
Parowan, UT
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N9892JCessna 172N
Weather
Visual (VMC) · Night
Status
Completed · report September 29, 2004
Report
Approved by Office Director
Parties
Salt Lake City FAA FSDO
FAA report
20040212001839A
Case key
58763

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

the pilot's in-flight decision/planning which resulted in fuel exhaustion. The fence and night conditions were contributing factors.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of engine power(total) - nonmechanicalCruise
In-flight planning/decision - improperPilot in commandCause
Fuel system - exhaustionFactor
Forced landingEmergency descent/landing
In flight collision with objectEmergency descent/landing
Object - fenceFactor
Light condition - night

Analysis

According to the pilot, he topped-off the airplane with fuel, and departed to the west on a long cross-country flight. After flying for several hours, he saw the "glow of [city] lights" and thought it was his destination. He attempted to contact the airport by radio, but did not receive a response. He stated that, at that time, he was unable to pick up the VOR. At that point he realized that he must have drifted north and off of his intended heading. He said he adjusted his heading to the southwest, and climbed to a higher altitude. Shortly thereafter, he located his destination, and through radio contact, turned on the runway lights. As he flew over the airport, the airplane's engine began to lose power and then it "cut out." He circled around the airport as he descended and set up for a forced landing on runway 22. On the final approach, he realized that he wasn't going to make the runway. He said that he "increased the [airplane's] angle of attack," but the airplane fell short of the runway. The airplane's right wing struck a fence post and the airplane impacted the terrain approximately 50 yards short of the runway threshold. The airplane's right wing spar was bent outboard of the wing strut, and the nose landing gear was separated from the gear fork. An on-site examination of the airplane revealed that both wing fuel tanks were empty.

Factual narrative

On February 12, 2004, at approximately 2300 mountain standard time, a Cessna 172N, N9892J, operated by Pro-Air Aviation, LLC., was substantially damaged when it struck a fence during a forced landing at Parowan Airport (1L9), Parowan, Utah. The private pilot and his passenger were not injured. Night visual meteorological conditions prevailed. A visual flight rules flight plan was filed for this personal cross-country flight being conducted under Title 14 CFR Part 91. The flight to Cedar City, Utah, originated at Albuquerque, New Mexico, at approximately 1830.

According to the pilot, he stated that he had flown the route between Albuquerque and Cedar City four previous times. Prior to departing Albuquerque, he said he "filled up with fuel." They departed Albuquerque, and flew on a heading of 280 degrees over Page, Arizona. From Page, he flew a heading of 290 degrees. As he cleared the mountains, he saw the "glow of [city] lights" and thought it was Cedar City. He attempted to contact the Cedar City Airport by radio, but did not receive a response. He also stated that, at that time, he was unable to pick up Cedar City's VHF Omni-directional Radio range (VOR). At that point, he realized that he must have drifted north and off of his intended heading, and identified that the city was not Cedar City.

He said he adjusted his heading to the southwest, and climbed up to 11,000 feet (msl). Shortly thereafter, he saw Parowan, Utah, and through radio contact, turned on the runway lights. As he flew over Parowan Airport, the airplane's engine began to lose power and then it "cut out." He circled around the airport as he descended and set up for a forced landing on runway 22. On the final approach, he realized that he wasn't going to make the runway. He said that he "increased the [airplane's] angle of attack," but the airplane fell short of the runway. The airplane's right wing struck a fence post and the airplane impacted the terrain approximately 50 yards short of the runway threshold. The airplane's right wing spar was bent outboard of the wing strut, and the nose landing gear was separated from the gear fork.

According to an FAA inspector, an on-site examination revealed that both wing fuel tanks were empty.

Aircraft

Registration
N9892J
Reported as
Cessna 172N
Category
Airplane
Serial number
17273952
Airframe hours
7,206
Engine
Lycoming O-320-H2AD, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Pro Air Aviation LLC.
Airworthiness certificate
Standard, Normal
Last inspection
Annual · January 20, 2004 · 61.6 hours before
Departed
AEG · Albuquerque, NM
Destination
CDC · Cedar City, UT
Flight plan
VFR
Airport
1L9 · Parowan Airport, runway 220, 5,000 × 75 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
19
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 1, Valid Medical--no waivers/lim.
Seat
Left
Flight hours
152 total · 135 in this make and model · 95 as pilot in command · 86 in the last 90 days · 14 in the last 30 days · 5 in the last 24 hours

Weather

Conditions
Visual (VMC) · Night
Wind
0° at 0 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
9 °F, dew point 3 °F
Altimeter
30.28 inHg
Observed at
KCDC, 16 nm away

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.

Other investigations on N9892J · 1

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