ANC15LA057 · Found Acft Canada Inc FBA 2C1
United States Fish and Wildlife Service Found Acft Canada Inc FBA 2C1 · Accident: collision during takeoff/landing
From Cape Sarichef Airport (26AK) to Cold Bay Airport (CDB)
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
- ANC15LA057
- 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
- Government
- 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
Found Acft Canada Inc FBA 2C1
- Aircraft type
- Found FBA-2
- 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
- N798
- Onboard fatalities
- Unknown
- Route
- From Cape Sarichef Airport (26AK), Cold Bay, AKTo Cold Bay Airport (CDB), COLD BAY, AK
- Aircraft age
- About 13 years (built 2002)
- 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
- Public Aircraft
- 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
- Takeoff
- 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
- Collision during takeoff/landing
- 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 › Physical environment
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot reported that, during a local public flight, he attempted to take off from an unimproved airstrip that included a dogleg right turn. About 100 ft after making the required turn, the pilot realized that he had not corrected enough to the right to get lined up with the straight portion of the takeoff area and that the airplane was drifting left. His failure to maintain adequate distance from surrounding terrain resulted in the airplane contacting a 5-ft-high berm, inadvertently becoming airborne, and entering an aerodynamic stall. The airplane subsequently impacted the tundra in a left-wing-down attitude, bounced, and then came to rest about 180 degrees from the takeoff heading.
Probable cause
The pilot's failure to maintain adequate distance from surrounding terrain during the takeoff sequence, which resulted in the airplane contacting the terrain, prematurely becoming airborne, and subsequently entering an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC15LA057
- Event ID
- 20150727X90643
- Case number
- ANC15LA057
- 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: 06eb040dc02871d22ff97b3a0e4a28d88f6b0552843dddc40c222842bc695b02; retrieved 2026-09-16T02:35:11.846Z.