Inland Aviation Services Cessna 207 accident
Cessna 207 · Accident: in flight collision with terrain/water en route
From 47 MILE CREEK, AK to Aniak Airport (ANI)
Event
- NTSB case
- ANC00FA128
- 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
- 0
- 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
- Not recorded
Cessna 207
- Aircraft type
- Cessna 207
- 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
- N42472
- Operator
- Inland Aviation Services
- Onboard fatalities
- Unknown
- Route
- From 47 MILE CREEK, AKTo Aniak Airport (ANI), Aniak, 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 · climb to 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
- 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, initiated
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The air taxi pilot had flown to a remote airstrip and lodge in a company airplane to go hunting. He was scheduled the next morning for a flight from his company's base of operations, his original departure airport. According to a hunting guide at the lodge, the pilot departed the lodge's airstrip about 0608, with a load of revenue cargo. A few minutes later, the guide heard the sound of an airplane, and then a loud impact. The guide could not see the wreckage because it was too dark outside. He departed in his own airplane, but entered clouds shortly after takeoff, and had to return. The guide commented he thought the accident pilot was trying to return to the lodge airstrip because of the poor weather and darkness. The wreckage was located on a nearby mountain in daylight hours after the cloud cover had dissipated. Postaccident inspection disclosed no evidence of any preimpact mechanical anomalies with the airplane. Official sunrise was 0813; official civil twilight was 0730. The time of the accident was approximately 0615.
Probable cause
The pilot's decision to initiate visual flight into dark night instrument meteorological conditions. Factors associated with the accident are a low ceiling, a dark night, the pilot's failure to follow regulatory procedures and directives, and his self-induced pressure to return to base to take another flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC00FA128
- Event ID
- 20001212X21881
- Case number
- ANC00FA128
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: a039bebfb48807afa0968fb211c2178b69340b004ff7acb541e3f2cce664d920; retrieved 2026-09-18T13:11:33.246Z.
- The NTSB's operator name is blank for N42472; the operator shown is the name the NTSB records it doing business as.