Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

February 19, 2018 · Cessna 172 N · N7328F

Obyan, OF, CQ

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 19, 2018
Injury Outcomes
2 injuries (2 minor injuries)
Location
Obyan, OF, CQ
Aircraft
Cessna 172 N (1979)
Tail Number
N7328F
Operator
Star Marianas Air
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
WPR18LA092

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.

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

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

Flight

Event TypeAccident
Event Time07:30 UTC
Nearest AirportFrancisco C Ada/Saipan Intl (3959nm W)
Runway25
Runway Length8700 ft
Runway Width200 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172 N
Tail NumberN7328F
Aircraft CategoryAir
DamageSubstantial
OperatorStar Marianas Air
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 SERIES · Reciprocating · 160
Seats4

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 25 · First Class · Minor
Crew 2Minor

Conditions

ConditionsVMC
LightDaylight
Wind70° @ 13 kt
Visibility10 sm
CeilingNone
Altimeter29.87 inHg
Observation Time06:54
Weather SourceWFAC

Appendix: Source Data