ANC03LA044 · Piper PA-32-300
Piper PA-32-300 · Accident: in flight collision with terrain/water en route
From Ralph Wien Memorial Airport (OTZ) to Robert (Bob) Curtis Memorial Airport (ORV)
Event
- NTSB case
- ANC03LA044
- 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
- 0 · 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
Piper PA-32-300
- Aircraft type
- Piper PA-32
- 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
- N2863T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ralph Wien Memorial Airport (OTZ), Kotzebue, AKTo Robert (Bob) Curtis Memorial Airport (ORV), Noorvik, 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
- 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 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
- Substantial
Cause areas
- Pilot in command › Altitude/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
The solo commercial pilot reported he was transporting cargo on a cross-country flight in VFR conditions. The flight progressed over a large, featureless, snow-covered lagoon, and according to the pilot, flat light conditions made it difficult to discern any topographical features of the terrain. The pilot didn't realize that the airplane had entered a descent. The airplane descended and ultimately struck the snow-covered lagoon, sustaining substantial damage to the wings and fuselage. The pilot reported that there were no preaccident mechanical anomalies with the airplane. The reported weather conditions included a 1,200 foot overcast ceiling and visibility of 9 statute miles.
Probable cause
The pilot's failure to maintain adequate altitude/clearance, which resulted in an in-flight collision with terrain during cruise flight. Factors associated with the accident were flat light conditions, and snow-covered terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC03LA044
- Event ID
- 20030418X00528
- Case number
- ANC03LA044
- 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: 076f662c739df1d3246243c42ce81d8103de03e1d7baee74c33727f6b1a6e4f3; retrieved 2026-09-18T15:51:38.357Z.