FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Strait Air (2000) Piper PA31 310 accident

3 May 2017 · Colton, NY, United States

Piper PA31 310 · Accident en route

From Quebec Jean Lesage International Airport (CYQB) to Montréal / Saint-Hubert Metropolitan Airport (CYHU)

Report a problem

Event

NTSB case
ERA17FA172
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
1 · 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

Piper PA31 310

Aircraft type
Piper PA31
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
C-GQAM
Onboard fatalities
Unknown
Route
From Quebec Jean Lesage International Airport (CYQB), QuebecTo Montréal / Saint-Hubert Metropolitan Airport (CYHU), Saint Hubert
Aircraft age
About 38 years (built 1979)
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
Non-U.S., Commercial
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
Miscellaneous/other
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

  • Not determined › Not determined
  • Personnel issues › Physical

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

NTSB narrative

The commercial pilot departed on a planned 1-hour cargo cross-country flight in the autopilot-equipped airplane. About 3 minutes after departure, the controller instructed the pilot to fly direct to the destination airport at 2,000 ft mean sea level (msl). The pilot acknowledged the clearance, and there were no further radio transmissions from the airplane. The airplane continued flying past the destination airport in straight-and-level flight at 2,100 ft msl, consistent with the airplane operating under autopilot control, until it was about 100 miles beyond the destination airport.

A witness near the accident site watched the airplane fly over at a low altitude, heard three "pops" come from the airplane, and then saw it bank to the left and begin to descend. The airplane continued in the descending left turn until he lost sight of it as it dropped below the horizon.

The airplane impacted trees in about a 45° left bank and a level pitch attitude and came to rest in a heavily wooded area. The airplane sustained extensive thermal damage from a postcrash fire; however, examination of the remaining portions of the airframe, flight controls, engines, and engine accessories revealed no evidence of preimpact failure or malfunction. The fuel selector valves were found on the outboard tanks, which was in accordance with the normal cruise procedures in the pilot's operating handbook. Calculations based on the airplane's flight records and the fuel consumption information in the engine manual indicated that, at departure, the outboard tanks of the airplane contained sufficient fuel for about 1 hour 10 minutes of flight. The airplane had been flying for about 1 hour 15 minutes when the accident occurred. Therefore, it is likely that the fuel in the outboard tanks was exhausted; without pilot action to switch fuel tanks, the engines lost power as a result of fuel starvation, and the airplane descended and impacted trees and terrain.

The overflight of the intended destination and the subsequent loss of engine power due to fuel starvation are indicative of pilot incapacitation. The pilot's autopsy identified no significant natural disease: however, the examination was limited by the severity of damage to the body. Further, there are a number of conditions, including cardiac arrhythmias, seizures, or other causes of loss of consciousness, that could incapacitate a pilot and leave no evidence at autopsy.

The pilot's toxicology results indicated that the pilot had used marijuana/tetrahydrocannabinol (THC) at some point before the accident. THC can impair judgment, but it does not cause incapacitation; therefore, the circumstances of this accident are not consistent with impairment from THC, and, the pilot's THC use likely did not contribute to this accident. The reason for the pilot's incapacitation could not be determined.

Probable cause

The pilot's incapacitation for unknown reasons, which resulted in an overflight of his destination, a subsequent loss of engine power due to fuel starvation, and collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA17FA172
Event ID
20170503X23550
Case number
ERA17FA172
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2017-05-04.
  • API snapshot SHA-256: 4df3e36ef3814763cee249c7f7aa590f89857c658f6d1cbb0066d0a6513b91ca; retrieved 2026-09-15T06:02:02.812Z.