ASN Wikibase Occurrence # 163154
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Friday 10 January 2014 |
| Time: | 19:48 |
| Type: |  Cessna 310R |
| Owner/operator: | Royal Air Freight, Inc |
| Registration: | N3829G |
| MSN: | 310R0924 |
| Year of manufacture: | 1977 |
| Total airframe hrs: | 4427 hours |
| Engine model: | Continental IO-520-MB |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Oakland County International Airport (KPTK), Pontiac, MI -
 United States of America
|
| Phase: | Approach |
| Nature: | Ferry/positioning |
| Departure airport: | Atlanta, GA (FTY) |
| Waterford, MI (PTK) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The airplane, operated by an on-demand cargo carrier and flown by a newly hired pilot, was on a positioning flight when it impacted trees and terrain about 1,500 ft short of the runway during a straight-in instrument landing system (ILS) approach. Night instrument flight rules (IFR) conditions prevailed with recorded weather observations that were below the minimum visibility specified for the approach. Radar data showed that while on the final segment of the ILS approach, the airplane's approach was unstabilized in speed and position along the glidepath. The shallow angle of the wreckage path and its length were consistent with controlled flight into terrain. Examination of the wreckage revealed no anomalies that would have precluded normal aircraft operation.
The pilot had undergone company training provided by the company's president, who was also the director of operations, and the chief pilot; these two individuals were the only company instructors approved by the Federal Aviation Administration (FAA) to provide Part 135 training in accordance with the company training manual. However, the majority of the pilot's flight training in the accident airplane make and model was during a flight with a company pilot who was not approved by the FAA to provide Part 135 instruction. Further, although company records stated that the pilot met the training requirements for ground and flight training in accordance with the company training manual, the minimum flight times in the accident airplane make and model were not met and the method of ground instruction was not followed in accordance with the company training manual.
A review of the weather for the pilot's previous company flights showed that he had not flown in actual conditions that were at approach minimums at night, similar to those at the time of the accident. The chief pilot stated that higher approach weather minimum limitations were placed upon the pilot and that company dispatchers watched most new pilots' minimums until they got more experience with the company. However, although the dispatch manager indicated he was aware of weather limitations for the pilot, he stated that the dispatchers had no means of routinely communicating with the pilots inflight, and he could not recall when there had been any other pilots with weather limitations. Furthermore, there was no FAA-approved program or policy within the company operations specifications or other manual for higher approach minimum limitations based upon experience for company pilots of piston engine powered airplanes such as the accident airplane.
Probable Cause: The pilot's controlled flight into terrain during an instrument landing system approach at night in instrument flight rules conditions. Contributing to the accident were the operator's inadequate training of the pilot, the operator's failure to provide a level of oversight commensurate to the pilot's experience, and the pilot's lack of operational experience in actual night instrument conditions in the make and model of the airplane.
Accident investigation:
 |
|
Sources:
NTSB
https://flightaware.com/live/flight/RAX907
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=3829G
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 11-Jan-2014 02:38 | Geno | Added |
| 11-Jan-2014 03:34 | Geno | Updated [Aircraft type, Operator, Nature, Departure airport, Destination airport, Source, Damage, Narrative] |
| 11-Jan-2014 03:52 | Geno | Updated [Source, Narrative] |
| 13-Jan-2014 17:34 | Geno | Updated [Registration, Cn, Source] |
| 14-Jan-2014 22:39 | Geno | Updated [Time, Nature, Destination airport, Source] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 29-Nov-2017 13:22 | ASN Update Bot | Updated [Cn, Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation