FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC16FA052 · Cessna 210-5

5 Aug 2016 · Wasilla, AK, United States

Cessna 210-5 and de Havilland DHC 2 T · Accident: midair collision during landing

Report a problem

Event

NTSB case
ANC16FA052
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
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

Aircraft 1 · Cessna 210-5

Aircraft type
Cessna 210
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
N1839Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Merrill Field (MRI), Anchorage, AKTo Wasilla Airport (IYS), Wasilla, AK
Aircraft age
About 54 years (built 1962)
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
Landing
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
Substantial

Aircraft 2 · de Havilland DHC 2 T

Aircraft type
de Havilland DHC-2
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
N30CC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Leisurewood Airstrip Owners Assoc Airport (9AK6), Wasilla, AKTo Wasilla Airport (IYS), Wasilla, AK
Aircraft age
About 52 years (built 1964)
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
Landing
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
Substantial

Cause areas

  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor and student pilot on board the Cessna were conducting practice takeoffs and landings using the airport's published right-turn traffic pattern. At the same time, the commercial pilot of a single-engine de Havilland airplane departed an airport 5 miles to the north, proceeded to the airport and turned onto the final leg of the traffic pattern for landing. The instructor on board the Cessna reported that, during their fourth landing, just as the student began the landing flare, there was a sudden loud noise, and the airplane abruptly nosed down and impacted the runway. The instructor reported that he did not hear or see the other airplane before the collision. The pilot of the de Havilland reported that neither he nor his passenger heard any radio transmissions from the Cessna, and they did not see the Cessna in the traffic pattern until impact. The pilot stated that, about 70 ft above the runway surface, the Cessna overtook the de Havilland from directly above, impacting the propeller. The pilot was able to maintain control and subsequently landed the airplane.

A postaccident examination of both airplanes, revealed signatures consistent that the initial impact sequence was between the empennage of the Cessna and the propeller assembly of the de Havilland. The pilots for both airplanes reported no mechanical anomalies that would have prevented the airplanes from maneuvering to avoid an impact.

Day visual meteorological conditions prevailed in the area, and neither airplane was in communication with air traffic control; the airport was not equipped with a control tower. A recording of transmissions made on the airport's common traffic advisory frequency (CTAF) revealed that, although the Cessna instructor made radio transmissions throughout the first three traffic patterns; no radio transmissions were heard from the Cessna pilots during the final (accident) traffic pattern. The de Havilland pilot stated his airplane's position before entering the traffic pattern and again on the final leg announcing his intent to land.

Postaccident examination and testing of the two radios in the Cessna revealed no mechanical anomalies. Additionally, the radios in both airplanes were tuned to the correct frequency for the airport CTAF. The Cessna instructor reported the he made a radio transmission during the final traffic pattern. It was undetermined why no CTAF radio transmission from the Cessna was heard on the CTAF recording for the accident traffic pattern.

Neither airplane was equipped with an Automatic Dependent Surveillance – Broadcast (ADS-B) system or cockpit display of traffic information. Had both airplanes been fully equipped with an ADS-B system capable of both transmitting and receiving position data and issuing traffic alerts via cockpit display, each pilot would have been alerted to the presence of the other airplane, and it is likely that the collision would have been avoided.

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.

OpsVue track data showed the flights paths for both airplanes as coming from opposite directions for the landing. It is likely that the pilots had relaxed their vigilance in looking for traffic when operating in the airport environment. 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.

See-and-Avoid Concept

According to 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 landing at a non-tower-controlled airport, which resulted in a midair collision. Contributing to the accident was the absence of radio calls from the Cessna during the traffic pattern preceding the accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC16FA052
Event ID
20160805X34814
Case number
ANC16FA052
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: 4a9b04c0a70dcad85c71081fa43c9511e7bce8f708087acb4165701d5f444c6a; retrieved 2026-09-13T18:25:34.011Z.