FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

South Central Air Cessna 207 accident

16 Oct 1993 · Kenai, AK, United States Possible conflict

Cessna 207 · Accident: in flight collision with terrain/water en route

From an unrecorded airport to Homer Airport (HOM)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ANC94FA011
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
Unknown

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
N208SC
Onboard fatalities
Unknown
Route
From not recordedTo Homer Airport (HOM), Homer, 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
Destroyed

Cause areas

  • Pilot in command › Proper altitude, not maintained

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

NTSB narrative

THE PILOT REPORTEDLY FLEW A ROUTE ALONG THE POWER LINES BETWEEN KENAI AND HOMER. THE FLIGHT TOOK PLACE ON A DARK MOONLESS NIGHT OVER RISING TERRAIN. THE ACCIDENT SITE WAS LOCATED 200 YARDS EAST OF THE POWER LINES. RADAR DATA SHOWS THE AIRPLANE IN THE AREA OF THE CRASH SITE AT A STEADY STATE HEADING, AIRSPEED, AND LEVEL ALTITUDE. THIS FLIGHT MARKED THE FIRST TIME THAT THE PILOT DID NOT COMPLETE A COMPANY FLIGHT PLAN. ON HIS OFF DAYS, THE PILOT GOT 9-11 HRS OF SLEEP. HIS WIFE SAID HE WAS NOT A MORNING PERSON. THE PILOT HAD COMMENTED TO HER THAT WHEN AWAY FROM HOME, THE QUALITY OF HIS SLEEP WAS POOR. ON THE DAY OF THE ACCIDENT, THE PILOT WAS AWAKE AT 0340 FOR THE 0500 DEPARTURE; HE HAD ABOUT 6 HRS OF SLEEP.

Probable cause

THE PILOT'S FAILURE TO MAINTAIN ADEQUATE ALTITUDE FOR TERRAIN CLEARANCE. FACTORS WHICH CONTRIBUTED TO THE ACCIDENT WERE: THE PILOT'S LACK OF USUAL SLEEP, THE NIGHT LIGHT CONDITION AND HILLY TERRAIN.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC94FA011
Event ID
20001211X13499
Case number
ANC94FA011
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. 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: c7157e817ef5c9d0ef7cbd56aa762f97aadfa5a1d58d3800b5ba0cfb2314f64c; retrieved 2026-09-18T13:51:33.139Z.
  • The NTSB's operator name is blank for N208SC; the operator shown is the name the NTSB's other records give its FAA operator code, SOCA.