Smokey Bay Air Cessna T207 UNDESIGNAT accident
Cessna T207 UNDESIGNAT · Accident: abnormal runway contact during landing
From Port Graham Airport (PGM) to Nanwalek Airport (KEB)
Event
- NTSB case
- GAA16CA445
- 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
- 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
Cessna T207 UNDESIGNAT
- 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
- N91025
- Operator
- Smokey Bay Air
- Onboard fatalities
- Unknown
- Route
- From Port Graham Airport (PGM), Port Graham, AKTo Nanwalek Airport (KEB), Nanwalek, AK
- Aircraft age
- About 47 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
- Landing · landing roll
- 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
- Abnormal runway contact
- 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
- Pole
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that during landing the wind sock at the airport indicated that the wind was variable, about 5 knots, and predominately favored runway 1.
According to the FAA airport facility directory, runway 01/19 was 1,850 feet long, and soft gravel. However, 1,000 feet of northern portion of the runway was closed indefinitely.
The pilot recalled that about 500 feet down the 1,850 foot runway, and just before touchdown the airplane encountered, "a pretty rapid shift in the winds in both direction and velocity." He reported that the airplane touched down momentarily, and then went airborne again. After the second touchdown, the speed did not decline as expected, and although the airplane did start to slow as it got a better grip on the gravel (which was wet from rain that had occurred earlier), he ran out of runway. He reported that the airplane overran the runway at a groundspeed of about 10 knots, went down a small embankment, had a propeller strike and the airplane sustained substantial damage when the left wing struck a post.
The pilot reported that there were no mechanical malfunctions or anomalies during the flight that would have prevented normal flight operations.
The pilot reported that he considered going around, but due to the wind and terrain rejected the idea.
Probable cause
The pilot’s unstabilized approach and a subsequent runway overrun while landing on a short runway in variable wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA445
- Event ID
- 20160823X90755
- Case number
- GAA16CA445
- 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: e550fb59fcaf2465c64aa31887c463e23573fe888945104c1872b8d8feb0acde; retrieved 2026-09-16T04:11:20.181Z.