ASN Wikibase Occurrence # 162663
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: | Sunday 8 December 2013 |
| Time: | 18:21 |
| Type: |  Cessna 310R |
| Owner/operator: | Private |
| Registration: | N98BT |
| MSN: | 310R1582 |
| Year of manufacture: | 1979 |
| Total airframe hrs: | 4161 hours |
| Engine model: | Continental IO-550-A |
| Fatalities: | Fatalities: 3 / Occupants: 3 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | South of Jacksonville Executive Airport (KCRG), Jacksonville, FL -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Fort Pierce, FL (FPR) |
| Jacksonville, FL (CRG) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot filed an instrument flight rules (IFR) flight plan with flight services, and the briefer asked the pilot if he would like weather information. The pilot replied “no,” and stated that the weather “looked good”; however, at that time, the weather at the destination airport included visibility of 2 miles and a 400-foot overcast ceiling. The pilot proceeded on the approximate 1-hour night flight to the destination airport in low IFR conditions. During the instrument landing system approach, the pilot flew about 1 mile right of and 900 feet below the final approach fix. The tower controller issued a low altitude alert and instructed the pilot to check his altitude. The pilot acknowledged the instruction and confirmed that the airplane’s altitude was 600 feet, which was the altitude indicated on radar. He then flew the airplane left of the final approach course twice before intercepting it a third time, descending to 300 feet, and then reporting that he was going to conduct a missed approach.
The published missed approach procedure was to climb to 700 feet and then to make a climbing right turn to 1,900 feet on a 180-degree heading. However, the tower controller instructed the pilot to fly a heading of 280 degrees, and the pilot acknowledged the instruction. The controller did not provide an altitude and was not required to do so. After the pilot acknowledged the instruction, the airplane made a climbing left turn to 900 feet before radar and radio communications were lost. The airplane subsequently descended and collided with a retaining pond near the last recorded radar target. Although the tower controller’s issuance of nonstandard missed approach instructions without specifying an altitude might have added to the pilot’s workload, radar data show an initial turn consistent with the instructions and an associated climb indicating that the nonstandard instructions were not a factor in the accident. Examinations of the airplane and engine revealed no preimpact mechanical malfunctions that would have precluded normal operation, and there was no evidence of medical impairment that would have affected the pilot’s performance.
Given the night instrument meteorological conditions (IMC) with restricted visibility and the sustained left turn and climb, it is likely the pilot experienced spatial disorientation. The investigation could not determinate the pilot’s overall and recent experience in actual IMC; however, his inability to align the airplane with both the final approach fix’s lateral and vertical constraints is consistent with a lack of instrument proficiency.
Probable Cause: The pilot’s failure to maintain airplane control during a missed approach in night instrument meteorological conditions due to spatial disorientation and a lack of instrument proficiency.
Accident investigation:
 |
|
Sources:
NTSB
https://flightaware.com/live/flight/N98BT
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=98BT
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 09-Dec-2013 02:21 | Geno | Added |
| 09-Dec-2013 04:29 | Geno | Updated [Aircraft type, Registration, Cn, Operator, Phase, Departure airport, Destination airport, Source, Narrative] |
| 09-Dec-2013 06:51 | Geno | Updated [Total fatalities, Total occupants, Other fatalities, Source, Narrative] |
| 09-Dec-2013 07:19 | Gene | Updated [Total fatalities, Total occupants, Other fatalities, Source, Narrative] |
| 09-Dec-2013 23:18 | Geno | Updated [Nature, Source, Damage, Narrative] |
| 27-Dec-2013 23:38 | Geno | Updated [Time, Source, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 19-Aug-2017 16:48 | ASN Update Bot | Updated [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