PINNACLE AIR INC

Certificate type not established

Data confidence: Records are linked by certificate number, aircraft registration, or a name match that a reviewer has confirmed. Each record below shows how it was linked.

Also recorded as: PINNACLE AIR INC

Accident & enforcement record

Events that happened, regardless of the operator's own reporting. Each links to its public source.

NTSB accidents & incidents

Accident · 2007-04-12 Operator named in NTSB report
Bombardier CL-600-2B19 (N8905F) No injuries Part 121

Operated by PINNACLE AIR INC (per NTSB report)

The pilots' decision to land at Cherry Capital Airport (TVC), Traverse City, Michigan, without performing a landing distance assessment, which was required by company policy because of runway contamination initially reported by TVC ground operations personnel and continuing reports of deteriorating weather and runway conditions during the approach. This poor decision-making likely reflected the effects of fatigue produced by a long, demanding duty day and, for the captain, the duties associated with check airman functions. Contributing to the accident were 1) the Federal Aviation Administration pilot flight and duty time regulations that permitted the pilots' long, demanding duty day and 2) the TVC operations supervisor's use of ambiguous and unspecific radio phraseology in providing runway braking information. The Safety Board's full report is available at http://www.ntsb.gov/publictn/A_Acc1.htm. The Aircraft Accident Report number is NTSB/AAR-08-02.

Source: NTSB case DCA07FA037
Accident · 2004-10-14 Operator named in NTSB report
Canadair CL-600 (N8396A) Fatal injury Part 91

Operated by PINNACLE AIR INC (per NTSB report)

(1) the pilots’ unprofessional behavior, deviation from standard operating procedures, and poor airmanship, which resulted in an in-flight emergency from which they were unable to recover, in part because of the pilots’ inadequate training; (2) the pilots’ failure to prepare for an emergency landing in a timely manner, including communicating with air traffic controllers immediately after the emergency about the loss of both engines and the availability of landing sites; and (3) the pilots’ improper management of the double engine failure checklist, which allowed the engine cores to stop rotating and resulted in the core lock engine condition. Contributing to this accident were (1) the core lock engine condition, which prevented at least one engine from being restarted, and (2) the airplane flight manuals that did not communicate to pilots the importance of maintaining a minimum airspeed to keep the engine cores rotating.

Source: NTSB case DCA05MA003

FAA enforcement actions

No FAA enforcement actions linked to this operator.

Maintenance disclosure history

No maintenance difficulty reports on file. Note: SDR filing is largely voluntary, so absence is not evidence of a clean maintenance history.

Linked aircraft

N-numberMake / modelYearStatusLink basis
N8396AOperator named in NTSB report
N8905FOperator named in NTSB report

Aircraft with earlier records under this certificate

Maintenance and accident records on this page also cover aircraft that are not in this operator's current FAA fleet list. Charter and management fleets change — owners switch management companies, sell, or export aircraft. Where the registry shows what became of a tail, it is noted below.

  • N8905F — records 2007 · no longer on the FAA registry
  • N8396A — records 2004 · no longer on the FAA registry