FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA03FA028 · Piper PA-28-181

18 Jan 2003 · Eastsound, WA, United States

Piper PA-28-181 · Accident: in flight collision with terrain/water while maneuvering

From Sequim Valley Airport (W28) to Orcas Island Airport (ORS)

Report a problem

Event

NTSB case
SEA03FA028
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
Visual Meteorological Cond

Piper PA-28-181

Aircraft type
Piper PA-28
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
N7282C
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sequim Valley Airport (W28), Sequim, WATo Orcas Island Airport (ORS), Eastsound, WA
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
Maneuvering
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

  • Pilot in command › Clearance, not maintained

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

NTSB narrative

At the time of departure for the 30 minute night flight to an island destination, the pilot set his altimeter to field elevation instead of to the broadcast barometric pressure from the nearby Automated Surface Observation System (ASOS). During the climbout, the pilot contact Air Traffic Control, which gave him an altimeter barometric pressure setting and advised him of radar contact passing 2,500 feet. At that point the pilot set his altimeter to an indicated altitude of 2,500 feet instead of at the correct barometric pressure setting. Upon arriving in the area of the destination airport, the pilot found it covered by a low-level fog layer. Without acquiring an updated altimeter setting from the ASOS on the neighboring island, or from the Automatic Terminal Information Service (ATIS) on the nearby mainland, he descended over the water in order to try to find a way to get to the airport underneath the fog. Just after leveling off at what his altimeter indicated was 500 feet, the aircraft impacted the water. It was ultimately determined that at no time during the flight did the pilot set the aircraft's altimeter in reference to an issued barometric pressure.

Probable cause

The pilot's failure to maintain clearance from the water and his failure to reset the altimeter to the local barometric pressure. Contributing factors were fog and night conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA03FA028
Event ID
20030205X00167
Case number
SEA03FA028
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2003-01-19.
  • API snapshot SHA-256: 3d68155612341cc582ea95647be8e4443e39c826eacd4deb341d7fe7371fb8b7; retrieved 2026-09-20T19:31:21.293Z.