FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03FA077 · Cessna 172N

25 Jan 2003 · Kalaupapa, HI, United States

Cessna 172N · Accident: in flight encounter with weather en route

From Daniel K. Inouye International Airport (HNL) to Kahului International Airport (OGG)

Report a problem

Event

NTSB case
LAX03FA077
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Cessna 172N

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N911FC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Daniel K. Inouye International Airport (HNL), Honolulu, HITo Kahului International Airport (OGG), Kahului, HI
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
In flight encounter with weather
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › VFR flight into imc, inadvertent

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The student pilot obtained an in-person weather briefing from the local flight service station (FSS) prior to departure for a solo cross-country flight between two islands. The printed weather information used to provide the briefing depicted visual flight rule (VFR) conditions throughout the planned route of flight. During the time the student was obtaining weather information and planning his flight, the flight instructor obtained a weather briefing from the FSS via telephone. Review of the recorded conversation between the weather briefer and the flight instructor revealed current and forecast weather conditions provided were above VFR weather minimums, and a recommendation discouraging VFR flight was not provided. The accident flight was the student's first solo cross-country. He had flown the same route of flight with his flight instructor 1 week prior to the accident. According to the flight instructor, the student planned to make the flight at 3,500 feet msl. The majority of the flight was to be over open ocean water along the north shore of an island with rugged mountainous terrain of elevations up to 4,961 feet msl. Review of radar data revealed the student pilot descended the airplane from 2,200 feet msl to as low as 1,000 feet msl as it traveled along the planned route. According to two military pilots, who were flying helicopters in the opposite direction along the same route and one of whom observed the accident airplane, the student was eventually going to encounter instrument meteorological conditions at the elevation he was flying. They reported the weather conditions as scattered clouds at 700 feet agl and broken clouds at 1,000 feet agl with precipitation and visibilities between 3 to 5 miles. Radar data depicted the airplane gaining altitude to about 1,500 feet msl before turning south toward higher terrain on the coast of the island. The wreckage was located at the 1,500-foot level of a steeply rising mountain. No preaccident anomalies were noted with the aircraft. According to the flight instructor, if her student could not see the next visual checkpoint during the cross-country flight, he was to turn around and return to the departure airport. Steep mountains separated the accident site from the closest weather reporting facility (11 miles away). The weather conditions at the reporting facility when the accident flight passed that location were a few clouds at 800 feet agl, scattered clouds at 2,400 feet agl, and broken clouds at 5,500 feet agl, with a visibility 10 miles.

Probable cause

the student pilot's inadvertent VFR flight into IMC, which resulted in his in-flight collision with mountainous terrain while maneuvering. A contributing factor was the low ceiling weather condition.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03FA077
Event ID
20030130X00132
Case number
LAX03FA077
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 73226e6e469259b2d47184eb1f59847604989fa5f60cf614363de0774d1af30a; retrieved 2026-09-20T19:29:57.000Z.