Air Logistics of Alaska Bell 206L-1 accident
Bell 206L-1 · Accident: total loss of engine power (mechanical failure) while maneuvering
From Metro Field (MTF) to Bettles Airport (BTT)
Event
- NTSB case
- ANC83FA144
- 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
- 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
- Visual Meteorological Cond
Bell 206L-1
- Aircraft type
- Bell 206
- Category
- Helicopter
- 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
- N1081K
- Operator
- Air Logistics of Alaska
- Onboard fatalities
- Unknown
- Route
- From Metro Field (MTF), Fairbanks, AKTo Bettles Airport (BTT), BETTLES, 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
- Maneuvering · hover
- 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
- Total loss of engine power (mechanical failure)
- 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
- Fuel contamination; Fuel starvation
- 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
- Fluid, fuel › Starvation
- Fuel system, screen › Inadequate
- Manufacturer › Acft/equip, inadequate design
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ACCORDING TO THE PLT, THE LOW FUEL WARNING LIGHT ILLUMINATED WHEN THE FUEL GAGE WAS INDICATING 200 LBS. HE REPORTED HE COULD SEE THE ARPT LIGHTS & ELECTED TO CONTINUE THE FLT. AFTER ARRIVING, HE TERMINATED HIS APCH TO A 30 TO 50 FT HOVER WITH NO FORWARD SPEED. AS HE APPLIED FORWARD CYCLIC TO HOVER TO THE REFUELING AREA, THE ENG FLAMED OUT. SUBSEQUENTLY, THE HELICOPTER LANDED HARD & THE MAIN ROTOR BLADES STRUCK THE TAIL BOOM. AN EXAM REVEAL THERE WAS ENOUGH FUEL REMAINING IN THE MAIN CELL FOR APRX 20 MIN OF FLT. DISASSEMBLY OF THE SYS REVEALED THAT DEBRIS (DIRT & ZINC CHROMATE PAINT CHIPS) WAS IN THE FILTERS. THE FILTER SCREEN HAD OPENINGS OF .020 INCH. PARTICLES WERE FOUND IN THE FLOW SWITCHES. HOWEVER, THE CLEARANCE BETWEEN THE FLOW SWITCH PLUNGER & THE WALL OF THE CASING WAS ONLY .012 INCH. EVIDENCE WAS FOUND TO INDICATE THIS RENDERED A FLOW SWICH INOPERATIVE SO THAT FUEL WOULD NOT TRANSFER FROM THE MAIN CELL TO THE REAR CELL WHERE IT COULD BE USED BY THE ENG.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ANC83FA144
- Event ID
- 20001214X43962
- Case number
- ANC83FA144
- 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: 1b9d3ef8a4baf41e53f8cb178a0421a4f991e6d9d68784d180242c719c380505; retrieved 2026-09-18T20:55:45.456Z.
- The NTSB's operator name is blank for N1081K; the operator shown is the name the NTSB records it doing business as.