FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Hallo Bay Air Cessna 180 accident

25 Jun 2003 · Anchor Point, AK, United States

Cessna 180 · Accident: in flight collision with terrain/water

From HALLO BAY, AK to Homer Airport (PAHO)

Report a problem

Event

NTSB case
ANC03LA067
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
3 · 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
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 180

Aircraft type
Cessna 180
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
N91303
Onboard fatalities
Unknown
Route
From HALLO BAY, AKTo Homer Airport (PAHO), Homer, AK
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 135: Air Taxi & Commuter
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
Unknown
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 collision with terrain/water
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

  • Reason for occurrence undetermined

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

NTSB narrative

The single engine, tundra tire-equipped airplane departed a remote wilderness lodge, located about 100 miles from the intended destination, on an on-demand air taxi flight with an airline transport certificated pilot and two passengers on board. A portion of the flight was over open ocean water. The airplane did not arrive at its destination, and no wreckage has been located. A fatally injured passenger was located in the ocean, 8 days after the airplane was reported overdue. The pilot and the remaining passenger were not located, and are presumed to have received fatal injuries. The airplane is presumed to have collided with ocean waters.

Probable cause

An in-flight collision with water for an undetermined reason.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC03LA067
Event ID
20030711X01069
Case number
ANC03LA067
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: 6ad61bb8ff4e6be5b0d04812cfeb3f046a9082eb2cfa1d9ea4491897d4216bb3; retrieved 2026-09-18T13:02:31.319Z.