Accident Cessna 310H N104DR,
ASN logo
ASN Wikibase Occurrence # 153277
 
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:Thursday 14 February 2013
Time:16:30
Type:Silhouette image of generic C310 model; specific model in this crash may look slightly different    
Cessna 310H
Owner/operator:Private
Registration: N104DR
MSN: 310H0021
Year of manufacture:1962
Total airframe hrs:5662 hours
Engine model:Continental IO-470
Fatalities:Fatalities: 3 / Occupants: 3
Aircraft damage: Destroyed
Category:Accident
Location:20 miles west of Vero Beach, FL -   United States of America
Phase: En route
Nature:Private
Departure airport:Sebastian, FL (X26)
Destination airport:Bartow, FL (BOW)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The noninstrument-rated pilot, copilot, and the passenger were attempting to return from the Bahamas to Florida; a weather front was passing over Florida at the time. The copilot had contacted flight service before the initial flight and learned of thunderstorms in the area; the flight had to divert from its planned destination. The copilot contacted flight service before a second flight, and the flight service specialist advised that visual flight rules flight was not recommended due to low cloud ceilings and visibility. The pilot decided to land at an airport closer to his destination. At that airport, the copilot again contacted flight service and remarked that he was trying to figure out how to "scud run" to get home. He also spoke to his wife, who told him that the weather "was bad" at their final destination, and she reported that she thought they would delay their flight until the next day. Even though his calls to the weather briefer and his wife indicated adverse weather along the route of flight and at the destination, the copilot likely advised the pilot to continue the flight. About 20 minutes into the flight, the copilot contacted the Orlando approach controller and reported that they had inadvertently entered instrument meteorological conditions (IMC). The controller instructed him to set the transponder code to 0311 so that she could locate the airplane and then to contact Miami Center; however, no further communications were received from the copilot.

Review of radar data revealed that, shortly after contacting Orlando Approach control, while the controller was attempting to locate the airplane, it descended in three left circuits from 8,900 feet mean sea level (msl) to 1,800 feet msl. It subsequently made a right circuit, descended to 900 feet msl, and continued to proceed toward the destination airport, eventually descending to 200 feet msl. The last 3 minutes of radar data showed the airplane flying at an altitude between 100 and 200 feet msl. The final radar target was recorded while the airplane was in a left circuit at 200 feet, about 1/8 mile southwest of the accident site. The wreckage was located the following day in a heavily wooded, deep water, swamp area, and no debris path was observed. Given the radar data and the existence of marginal visual conditions, moderate rain, and the pilot not being instrument rated, it is likely that the pilot experienced spatial disorientation.

Two toxicological tests revealed measurements of diphenhydramine in the pilot's blood at levels within or well above the therapeutic range indicating that the pilot likely took the drug about 2 to 3 hours before the accident. Diphenhydramine causes marked sedation and is also classed as a depressant and used as a sleep aid. Altered mood and impaired cognitive and psychomotor performance may also be observed. Therefore, it is very likely that cognitive and psychomotor impairment caused by diphenhydramine contributed to the pilot's poor judgment about flying in marginal weather conditions and may have further impaired his ability to appropriately cope with relatively unfamiliar flying conditions when he flew into IMC.
Probable Cause: The noninstrument-rated pilot's improper decision to continue visual flight rules flight into instrument meteorological conditions and his subsequent spatial disorientation. Contributing to the accident was the copilot's improper evaluation of the weather conditions after receiving several weather briefings for the flight. Also contributing to the accident was the pilot-in-command's cognitive and psychomotor impairment due to recent use of an overthecounter sedating antihistamine and the pilots' personal pressure to get home.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA13FA133
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB

Location

Revision history:

Date/timeContributorUpdates
15-Feb-2013 00:29 gerrard57 Added
15-Feb-2013 18:04 Geno Updated [Total fatalities, Total occupants, Other fatalities, Location, Departure airport, Destination airport, Source, Narrative]
16-Feb-2013 02:01 gerard57 Updated [Damage]
17-Feb-2013 13:42 Geno Updated [Time, Aircraft type, Registration, Cn, Departure airport, Source, Narrative]
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
28-Nov-2017 14:09 ASN Update Bot Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative]
04-Jul-2022 15:24 rvargast17 Updated [Damage]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org