ANC24FA094 · Cessna 207
Paklook Air Cessna 207 · Accident: controlled flight into terrain/object (CFIT) on approach
From Bethel Airport (BET) to an unrecorded destination
Event
- NTSB case
- ANC24FA094
- 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
- Ongoing
- API-reported fatalities
- 4 · 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
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
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
- N90193
- Operator
- PAKLOOK Air
- Onboard fatalities
- Unknown
- Route
- From Bethel Airport (BET), Bethel, AKTo not recorded
- Aircraft age
- About 55 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 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
- Approach
- 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
- Controlled flight into terrain/object (CFIT)
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On September 15, 2024, about 2204 Alaska daylight time, a Cessna 207 airplane, N90193, was destroyed when it was involved in an accident near St. Mary’s, Alaska. The pilot and three passengers were fatally injured. The flight was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. According to the operator, Yute Commuter Service, the airplane was reportedly being used by two employees for a personal flight at the time of the accident. Management personnel reported that the accident airplane was currently only being used for Part 91 operations since the engine had exceeded the manufacturers time before overhaul requirement. These Part 91 operations included company flight training and repositioning flights. The accident pilot, who was the assistant chief pilot for the operator, along with another company pilot, a former pilot for the operator, and a fourth passenger, intended to fly from Bethel Airport (BET), Bethel, Alaska, to St. Mary’s Airport (KSM), St. Mary’s, Alaska, for a moose hunt. According to the flight tracking service used by the operator, the airplane departed BET about 2108 and proceeded to the northwest to KSM between 500 and 800 ft above ground level (agl). At 2159, the airplane was about 4 nautical miles southeast of the KSM airport and about 180 ft agl over the Yukon River. The airplane continued north toward the airport, overflew the west side of runway 6/24, then maneuvered to the west of the airport. The airplane then made a left 180° turn and overflew runway 6/24 about 200 ft agl. The airplane turned right and proceeded south, then made a steep right descending turn toward the ground. The final recorded point was above the accident site (See figure 1).
Figure 1. Accident flight track near St. Mary’s Airport overlaid on Google Earth. According to the operator, the accident airplane was equipped with Automatic Dependent Surveillance–Broadcast (ADS–B), which provides aircraft position information via satellite navigation or other sensors and periodically broadcasts it, enabling the aircraft to be tracked. The information can be received by air traffic control ground stations as a replacement for secondary surveillance radar, as no interrogation signal is needed from the ground. However, no ADS-B data was received from the accident airplane, during the accident flight. According to archived Federal Aviation Administration (FAA) air traffic control radio communications, the accident pilot contacted the Anchorage Air Route Traffic Control Center (ARTCC) controller on-duty when the airplane was about 10 miles southwest of KSM and requested a special visual flight rules (SVFR) clearance to enter the KSM airport environment. The ARTCC controller subsequently provided the current weather conditions and issued the pilot a SVFR clearance. At 2155, the ARTCC controller instructed the pilot to change to the KSM airport advisory frequency and to report canceling the SVFR clearance once on the ground at KSM. At 2235, about 25 minutes after the facility-estimated arrival time at the airport, the controller attempted to contact the airplane with no response. An alert notice (ALNOT) was issued at 2300 for the overdue airplane. At 2156, KSM automated weather reported wind from 280° at 13 knots, visibility 2 1/2 miles with light rain and mist, ceiling overcast at 300 ft agl, temperature and dew point 8° Celsius (C) (46°F), altimeter setting 29.30 inches of mercury. Remarks: automated system with a precipitation discriminator, visibility 1 mile variable 5 miles, rain began at 2103 AKDT, hourly precipitation 0.01 inches, 6-hour rainfall 0.7 inches, temperature 7.8°C, dew point 7.8°C, 6-hour maximum temperature 8.9C, 6-hour minimum temperature 7.8C, 3-hour pressure tendency risen 3.7-hPa. The sunset at KSM occurred at 2110 and civil twilight ended and 2155. On the day of the accident, another company airplane departed BET on a scheduled 14 CFR Part 135 flight to KSM. According to the flight track data, the airplane arrived near KSM at 2128 and departed the area about 2135 without landing, and then returned to Bethel. The pilot of the airplane reported that weather conditions along the flight route to KSM were “going up and down a lot,” and the visibility went up to 10 miles at one point, but as they got closer to KSM, it was about 1 ¼ miles. Due to the weather, he turned around to return to Bethel, but then KSM went back up to 4 miles visibility. He turned back to KSM and requested a SVFR clearance from ARTCC. After receiving the clearance, the KSM visibility went down to ½ mile. As he approached KSM, he could see the hills surrounding the airport and Pitkas Point but could not see the runway environment; KSM appeared completely “fogged in,” so he canceled the SVFR approach and returned to BET. He added that the long runway 17/35 was closed at the time and the lights on runway 6/24 (the shorter runway) were inoperative. Since the wind was favoring runway 24, he had planned to land on the shorter runway. During his first attempt to land at KSM, he didn’t see any runways or the airport at all. During the approach, he could only see the surrounding hills and Pitkas Point, but not the runways or lights. He did attempt to activate the pilot-controlled runway lights for runway 17/35, but due to the reduced visibility he never saw the lights, the airport beacon, or any part of the runway environment at all. A senior National Transportation Safety Board (NTSB) investigator-in-charge (IIC), along with an FAA aviation airworthiness inspector, and an air safety investigator from Textron Aviation, responded to the accident site and examined the airplane wreckage on September 18. During the detailed on-scene examination, the investigative team documented the wreckage before recovery efforts began. The NTSB on-scene wreckage examination revealed that the airplane impacted rising terrain in a right wing low and nose low attitude on a northwest heading. The highly fragmented debris path was about 150 ft long and contained all major components of the airplane (See figure 2).
Figure 2. A view of the airplane wreckage at the accident site facing north (Courtesy of FAA). The airplane wreckage was recovered for the accident site and transported to Wasilla, Alaska, and a detailed NTSB examination is pending.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ANC24FA094
- Event ID
- 20240916195123
- Case number
- ANC24FA094
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2024-09-16.
- API snapshot SHA-256: a109b516b211c9f5e3c22ed7db6cb6c1842d274695360a15f46455095733111c; retrieved 2026-09-15T08:58:15.196Z.