J & M Alaska Air Tours Cessna 208B accident
Cessna 208B · Accident: abnormal runway contact during landing
From Tatitlek Airport (PAKA) to an unrecorded destination
Event
- NTSB case
- ANC25LA081
- 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
- Event fatalities
- Unknown
- 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 208B
- 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
- N645AT
- Operator
- J & M Alaska Air Tours
- Onboard fatalities
- Unknown
- Route
- From Tatitlek Airport (PAKA), Tatitlek, AKTo not recorded
- Aircraft age
- About 12 years (built 2013)
- 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
- 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
- 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
- Personnel issues › Action/decision
- 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
The operator reported that to comply with the straight-in arrival procedure at the airport, the pilot was required to make a steeper approach to the runway, and he did not decelerate the airplane to a normal landing speed during the approach. As the approach continued, the airplane passed over the runway threshold faster than anticipated, resulting in an inadvertent, midfield touchdown. After touchdown, the pilot determined that there was not enough runway to safely abort the landing, so he continued the landing roll. He applied reverse thrust and hard braking, but the airplane overran the runway, collided with an airport perimeter fence, crossed six lanes of traffic before coming to rest in an open grass field. The airplane sustained substantial damage to the right wing lift strut. The operator reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s decision to continue an unstabilized approach, which resulted in a landing touchdown with insufficient runway remaining and a subsequent runway overrun and a collision with a fence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC25LA081
- Event ID
- 20250802200685
- Case number
- ANC25LA081
- 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, cause areas. 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: de491652efa5acdb22a5f9eae6f20dae95202996d61c948f469a85b9fb9730a3; retrieved 2026-09-16T20:09:48.143Z.