North Star Air Cargo Short Brothers SC7 accident
Short Brothers SC7 · Accident: total loss of engine power (non-mechanical) on approach
From North Central West Virginia Airport (CKB) to Pittsburgh International Airport (PIT)
Event
- NTSB case
- IAD96FA147
- 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
Short Brothers SC7
- Aircraft type
- Short Brothers SC7
- 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
- N10DA
- Operator
- North Star Air Cargo
- Onboard fatalities
- Unknown
- Route
- From North Central West Virginia Airport (CKB), Clarksburg, WVTo Pittsburgh International Airport (PIT), Pittsburgh, PA
- 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
- Approach · IFR final approach
- 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 (non-mechanical)
- 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 exhaustion; Utility pole
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had flown this route in make and model airplane for nearly 4 years. He calculated 900 pounds of fuel were required for the flight, and saw 956 pounds on the fuel totalizer. The pilot was told by the ground controller of weather delays to his destination that ranged up to 2.5 hours. En route he was issued holding instructions with an EFC of 50 minutes later. After released from holding, 52 minutes after takeoff, the pilot was told that he was being vectored for a 35 mile final approach. The pilot then told the controller that he was fuel critical and the controller vectored him ahead of other airplanes. Ten minutes later, 84 minutes after takeoff, the controller asked his fuel status, and the pilot responded 'pretty low, seems like I'm losing oil pressure.' The pilot then advised the controller, 85 minutes after takeoff, that he shut down the right engine. He then declared an emergency and advised that he was not going to make the airport. Examination of the wreckage revealed the fuel tanks were intact, the fuel caps were secured, and the amount of fuel recovered from both tanks was 1.5 gallons, which was less than the specified unusable quantity. Company records showed that similar flights took about 48 minutes, and the airplane's average fuel flow was 580 pounds per hour.
Probable cause
The pilot's improper in-flight decision to continue to his destination when known en route delays were encountered which resulted in fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD96FA147
- Event ID
- 20001208X06750
- Case number
- IAD96FA147
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1996-09-17.
- API snapshot SHA-256: 2b4f11fe52a60cc596a7ed23390e988498adcab77e45ccc3ad70e218eba2b31e; retrieved 2026-09-18T17:46:32.418Z.