WPR18LA092

NTSB accident investigation · Cessna 172 · Obyan, Sark · February 19, 2018

Accident · Minor injuriesClass 3 · LimitedFinal report
Date
February 19, 2018, 17:30 local (07:30 UTC)
Place
Obyan, Sark
Injuries
2 minor
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N7328FCessna 172
Defining event
Enroute-climb to cruise: Loss of engine power (total)
Weather
Visual (VMC) · Day
Status
Completed
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Western Pacific Region
Parties
FAA-FSDO
FAA report
20180219012469A
Case key
96757

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 inadequate preflight fuel planning and inadequate in-flight fuel monitoring which resulted in a total loss of engine power due to fuel exhaustion and an emergency landing and subsequent impact with a ditch.

Findings · 3

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Planning/preparation: fuel planningPersonnel issues › Task performance · PilotCessna 172N: 5 casesAll aircraft: 719 casesProbable cause
Use of equip/info: use of equip/systemPersonnel issues › Task performance · PilotCessna 172N: 10 casesAll aircraft: 1,391 casesProbable cause
Fluids: fuelAircraft › Fluids/misc hardware · Fluid levelCessna 172N: 8 casesAll aircraft: 1,695 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

According to the operator, about 5 minutes after departure for a local, aerial observation flight, the engine began running roughly and then lost all power. While returning to the airport, the pilot was able to regain engine power momentarily by pumping the throttle control, but shortly after, the engine began to run roughly again, and the power decreased to 1,000 rpm. Subsequently, the pilot declared an emergency, and a tower controller cleared him to land. Due to the opposite direction departing airport traffic, the pilot chose to conduct a straight-in approach instead of a 360° turn to lose altitude. After landing, the airplane bounced several times, and the pilot then deliberately veered it off the runway. Subsequently, the airplane impacted a ditch and nosed over. The airplane sustained substantial damage to the wings, vertical stabilizer, and rudder. The pilot reported that he did not visually check the fuel tanks before departure and that he did not recall whether he looked at the fuel quantity indicators before or during the flight. The pilot did not report if he conducted any preflight fuel planning. The operator reported that the fuel logs did not indicate that the airplane had been fueled on the day of the accident. During examination of the airplane, no fuel was found in the wing tanks or carburetor bowl. A small amount of fuel was found in the gascolator bowl. No stains or other evidence was found at the accident site indicating that fuel had leaked from the airplane. Examination of the engine and airframe revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation. Although previous flight times and fuel records were not obtained during the investigation, given that the pilot did not check the fuel quantity before the flight, it is likely that his preflight fuel planning was inadequate because he did not ensure sufficient fuel was onboard for the flight and that he did not adequately monitor the fuel in flight, which led to fuel exhaustion and a subsequent total loss of engine power.

Factual narrative

On February 19, 2018, about 1730 Chamorro standard time, a Cessna 172N airplane, N7328F, was substantially damaged when it was involved in an accident at the Francisco C. Ada/Saipan International Airport (PGSN), Obyan, Northern Mariana Islands. The pilot and passenger sustained minor injuries. The airplane was operated as a Title14 Code of Federal Regulations Part 91 aerial observation flight. According to the operator, about 5 minutes after departure, the pilot reported that the engine began running roughly and then lost all power when the airplane was about 3 miles east of the airport and about 2,000 ft mean sea level. The pilot contacted a tower controller at the departure airport and reported that he intended to return to the airport, and the controller instructed him to enter the left downwind leg of the traffic pattern. While returning to the airport, the pilot was able to regain engine power by pumping the throttle control. While approaching the left downwind leg, the engine began to run roughly again, and the power decreased to 1,000 rpm. The pilot continued to pump the throttle control to no effect. Subsequently, the pilot declared an emergency, and a tower controller cleared him to land on an 8,700-ft-long, dry, asphalt runway. Due to the airport traffic in the area, the pilot chose to conduct a straight-in approach, instead of a 360° turn to lose altitude. According to a tower controller, the airplane was high and fast as it crossed the runway threshold and landed with about 1,000 ft of runway remaining. After landing, the airplane bounced several times, and the pilot subsequently deliberately veered it off the runway. Subsequently, the airplane impacted a ditch and nosed over. The pilot reported that he did not visually check the fuel in the tanks before departure. He subsequently reported that he did not recall whether he looked at the fuel quantity indicators before or during the flight. The pilot did not report if he conducted any preflight fuel planning. The operator reported that the fuel logs did not indicate that the airplane had been fueled on the day of the accident. The airplane’s previous flight times and fuel records were not obtained during the investigation. Examination of the airplane revealed that the wings, vertical stabilizer, and rudder had sustained substantial damage. No fuel was found in the tanks or the carburetor bowl during examination. A small amount of fuel was found in the gascolator bowl. No obvious stains or other evidence was found at the accident site indicating that fuel had leaked from the airplane. The gascolator was clear of debris. No fuel was found in the carburetor bowl. Examination of the engine and airframe revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation.

Aircraft

Registration
N7328F
Reported as
Cessna 172 (N)
Category
Airplane
Serial number
17273244
Built
1979
Airframe hours
631.7
Engine
Lycoming O-320 SERIES, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Aerial observation · Part 91
Operator
Star Marianas Air, Inc
Registered owner
Marianas Air Transfer Inc
Airworthiness certificate
Standard, Normal
Last inspection
AAIP · February 18, 2018 · 26 hours before
Departed
GSN · Obyan, OF
Destination
GSN · Obyan, OF
Airport
GSN · Francisco C Ada/Saipan Intl, runway 25, 8,700 × 200 ft, asphalt
Equipment
Stall warning system, Angle of attack indicator

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
25
Injuries
Minor
Certificate
Commercial
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 1, Without waivers/limitations
Last flight review
June 14, 2017
Seat
Right
Restraint
3-point
Flight hours
776 total · 179 in this make and model · 697 as pilot in command · 248 in the last 90 days · 124 in the last 30 days · 5 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
70° at 13 knots
Visibility
10 statute miles
Temperature
84 °F, dew point 73 °F
Altimeter
29.87 inHg
Observed at
PGSF, 1 nm away

Docket · 5

The files NTSB released with the investigation on February 18, 2021, on NTSB’s docket system: statements, records, photos and specialists’ reports. 5.9 MB in all.

FAA reports on this event · 1

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