Hageland Aviation Services Cessna 208 B accident
Cessna 208 B and Renfro's Alaskan Adventures Piper PA18 150 · Accident: midair collision en route
Event
- NTSB case
- ANC16FA061
- 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
- 5 · 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
Aircraft 1 · Cessna 208 B
- Aircraft type
- Cessna 208
- 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
- N752RV
- Operator
- Hageland Aviation Services
- Onboard fatalities
- Unknown
- Route
- From Russian Mission Airport (RSH), Russian Mission, AKTo Marshall Don Hunter Sr Airport (MDM), Marshall, AK
- Aircraft age
- About 2 years (built 2014)
- 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
- Defining eventThe 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Aircraft 2 · Piper PA18 150
- Aircraft type
- Piper PA18
- 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
- N82452
- Operator
- Renfro's Alaskan Adventures
- Onboard fatalities
- Unknown
- Route
- From Bethel Airport (BET), Bethel, AKTo Marshall, AK
- Aircraft age
- About 38 years (built 1978)
- 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
- Defining eventThe 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
- Midair collision
- 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
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The Cessna had departed about 3 minutes prior on a scheduled passenger flight and the Piper was en route to a remote hunting camp when the two airplanes collided at an altitude about 1,760 ft mean sea level over a remote area in day, visual meteorological conditions. The airline transport pilot and two passengers onboard the Cessna and the commercial pilot and the passenger onboard the Piper were fatally injured; both airplanes were destroyed. Postaccident examination revealed signatures consistent with the Cessna's outboard left wing initially impacting the Piper's right wing forward strut while in level cruise flight. Examination revealed no mechanical malfunctions or anomalies that would have precluded normal operation of either airplane. Neither pilot was in communication with an air traffic control facility and they were not required to be. A performance and visibility study indicated that each airplane would have remained a relatively small, slow-moving object in the other pilot's window (their fuselages spanning less than 0.5° of the field of view, equivalent to the diameter of a penny viewed from about 7 ft away) until about 10 seconds before the collision, at which time it would have appeared to grow in size suddenly (the "blossom" effect). From about 2 minutes before the collision, neither airplane would have been obscured from the other airplane pilot's (nominal) field of view by cockpit structure, although the Cessna would have appeared close to the bottom of the Piper's right wing and near the forward edge of its forward wing strut.
The Cessna was Automatic Dependent Surveillance-Broadcast (ADS-B) Out equipped; the Piper was not ADS-B equipped, and neither airplane was equipped with any cockpit display of traffic information (CDTI). CDTI data would have presented visual information regarding the potential conflict to both pilots beginning about 2 minutes 39 seconds and auditory information beginning about 39 seconds before the collision, providing adequate time for the pilots to react.
The see-and-avoid concept requires a pilot to look through the cockpit windows, identify other aircraft, decide if any aircraft are collision threats, and, if necessary, take the appropriate action to avert a collision. There are inherent limitations of this concept, including limitations of the human visual and information processing systems, pilot tasks that compete with the requirement to scan for traffic, the limited field of view from the cockpit, and environmental factors that could diminish the visibility of other aircraft. Given the remote area in which the airplanes were operating, it is likely that the pilots had relaxed their vigilance in looking for traffic.
The circumstances of this accident underscore the difficultly in seeing airborne traffic by pilots; the foundation of the "see and avoid" concept in VMC, even when the cockpit visibility offers opportunities to do so, and particularly when the pilots have no warning of traffic in the vicinity.
Due to the level of trauma sustained to the Cessna pilot, the autopsy was inconclusive for the presence of natural disease. It was undetermined if natural disease could have presented a significant hazard to flight safety.
See-and-Avoid Concept
According to Title 14 CFR 91.113, "Right-of-Way Rules," "when weather conditions permit, regardless of whether an operation is conducted under instrument flight rules or visual flight rules, vigilance shall be maintained by each person operating an aircraft so as to see and avoid other aircraft." In addition, FAA AC 90-48D, "Pilots' Role in Collision Avoidance," which was in effect at the time of the accident, stated that the see-and-avoid concept requires vigilance at all times by each pilot, regardless of whether the flight is conducted under instrument flight rules or VFR.
Probable cause
The failure of both pilots to see and avoid each other while in level cruise flight, which resulted in a midair collision.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC16FA061
- Event ID
- 20160831X62719
- Case number
- ANC16FA061
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: 3b3793f80b00c16526c95efded6e8a399a962f0b47d095e63ac364aa6f0f241a; retrieved 2026-09-13T18:08:58.011Z.