FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC18FA045 · Cessna 175

13 Jun 2018 · Anchorage, AK, United States

Cessna 175 and Spernak Airways Cessna 207 · Accident: midair collision en route

Report a problem

Event

NTSB case
ANC18FA045
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
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 175

Aircraft type
Cessna 175
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
N9423B
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Anchorage, AK
Aircraft age
About 60 years (built 1958)
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 · cruise
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 · 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
N91038
Onboard fatalities
Unknown
Route
From Anchorage, AKTo Tyonek, AK
Aircraft age
About 49 years (built 1969)
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
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Two wheel-equipped, high-wing airplanes, a Cessna 207 and a Cessna 175, collided midair while in cruise flight in day visual meteorological conditions. Both airplanes were operating under visual flight rules, and neither airplane was in communication with an air traffic control facility. The Cessna 175 pilot stated that he was making position reports during cruise flight about 1,000ft above mean sea level when he established contact with the pilot of another airplane, which was passing in the opposite direction. As he watched that airplane pass well below him, he noticed the shadow of a second airplane converging with the shadow of his airplane from the opposite direction. He looked forward and saw the spinner of the converging airplane in his windscreen and immediately pulled aft on the control yoke; the airplanes subsequently collided. The Cessna 207 descended uncontrolled into the river. Although damaged, the Cessna 175 continued to fly, and the pilot proceeded to an airport and landed safely. An examination of both airplanes revealed impact signatures consistent with the two airplanes colliding nearly head-on.

About 4 years before the accident, following a series of midair collisions in the Matanuska Susitna (Mat-Su) Valley (the area where the accident occurred), the FAA made significant changes to the common traffic advisory frequencies (CTAF) assigned north and west of Anchorage, Alaska. The FAA established geographic CTAF areas based, in part, on flight patterns, traffic flow, private and public airports, and off-airport landing sites. The CTAF for the area where the accident occurred was at a frequency changeover point with westbound Cook Inlet traffic communicating on 122.70 and eastbound traffic on 122.90 Mhz. The pilot of the Cessna 175, which was traveling on an eastbound heading at the time of the accident, reported that he had a primary active radio frequency of 122.90 Mhz, and a non-active secondary frequency 135.25 Mhz in his transceiver at the time of the collision. The transceivers from the other airplane were not recovered, and it could not be determined whether the pilot of the Cessna 207 was monitoring the CTAF or making position reports.

Probable cause

The failure of both pilots to see and avoid the other airplane while in level cruise flight, which resulted in a midair collision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC18FA045
Event ID
20180614X22730
Case number
ANC18FA045
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, 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: 34d4fe2f3751dcddb406c5f8de4740dd473909da09c4a168c13cc212ab1bf968; retrieved 2026-09-13T18:10:00.372Z.