FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

AirNet Systems Flight USC146

28 Nov 2013 · Montrose, PA, United States

Cessna 210L · Accident: loss of engine power (total) en route

From Teterboro Airport (TEB) to Buffalo Niagara International Airport (BUF)

Report a problem

Event

NTSB case
ERA14LA051
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 210L

Aircraft type
Cessna 210
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
N777BK
Onboard fatalities
Unknown
Route
From Teterboro Airport (TEB), Teterboro, NJTo Buffalo Niagara International Airport (BUF), Buffalo, NY
Aircraft age
About 39 years (built 1974)
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
En route · cruise
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
Loss of engine power (total)
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 › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that he had the airplane refueled before takeoff but that he did not check the fuel tanks for contaminants after fueling. The pilot performed an engine run-up before departure and reported no discrepancies. After departure, the airplane climbed to 8,500 feet mean sea level while proceeding toward the destination airport. After about 15 minutes in cruise flight, the pilot positioned the fuel selector to the left tank, and, about 15 minutes later, the engine lost power; however, the fuel flow increased to about 140 pounds per hour, and the fuel flow needle reached the maximum indication. The pilot's attempts to restore engine power were unsuccessful. The airplane was unable to maintain altitude, so the pilot used the on-board GPS receiver to locate the nearest airport; however, he realized that the airplane would be unable to reach the airport. He maneuvered the airplane for a forced landing on a road but again realized that he would be unable to reach that road. After descending below the clouds, he maneuvered the airplane for a landing on another road, and the airplane subsequently collided with an unmarked power line that crossed the road diagonally. The airplane contacted the ground and then came to rest upright.

Postaccident examination of the airplane revealed water contamination in both fuel tanks, the fuel strainer, and left header tank; however, no water was detected in the engine fuel system components; both of the fuel caps' seals were satisfactory. There were no reports of other airplanes fueled by the same truck having water contamination issues, and an examination of the truck used revealed that it was clean and in good repair. The source of the water could not be determined. The engine was removed from the airplane and placed in a test cell, and it was operated to near-full takeoff rpm with no discrepancies noted. Although no water was detected in the engine fuel system components, the excessive fuel flow reported by the pilot at the time of the total loss of engine power was consistent with water freezing at the manifold valve, which prevented the piston from allowing the fuel to flow to each cylinder.

Postaccident surveillance of the airline by its Federal Aviation Administration principal maintenance inspector revealed four instances in which other company pilots did not check the fuel tanks for contaminants after fueling, which was not in accordance with the operator's operations manual. After the accident, the company's director of operations issued flight operations bulletins reminding company pilots of the requirement to check the fuel tanks after fueling and the location of the fuel tank drains.

Probable cause

The pilot’s failure to check the fuel tanks for contaminants after fueling, which resulted in a total loss of engine power due to water contamination.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14LA051
Event ID
20131128X10038
Case number
ERA14LA051
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: d63d866fbf7235bd7879fb0346c1278d738b8bfdb018c9f3a6709ac1de3a2dd4; retrieved 2026-09-15T23:09:03.407Z.