Accident Cessna 172N Skyhawk N8405E,
ASN logo
ASN Wikibase Occurrence # 71532
 
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 17 January 2010
Time:10:04
Type:Silhouette image of generic C172 model; specific model in this crash may look slightly different    
Cessna 172N Skyhawk
Owner/operator:Tulip City Air Service
Registration: N8405E
MSN: 17272195
Year of manufacture:1979
Total airframe hrs:7379 hours
Engine model:Lycoming O-320-H2AD
Fatalities:Fatalities: 2 / Occupants: 2
Aircraft damage: Destroyed
Category:Accident
Location:South west of 136th Avenue and 58th Street, Manlius Township, MI -   United States of America
Phase: En route
Nature:Private
Departure airport:Tulip City, MI (BIV)
Destination airport:Tulip City, MI (BIV)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot rented the airplane for most of the day to give rides to friends and had fueled it to capacity. He told a lineman that he planned to takeoff and, if necessary, would file an instrument-flight-rules flight plan and return to the airport. Witnesses saw the airplane take off and disappear into the overcast. Shortly thereafter, they heard an airplane make four passes over the airport. The sound became progressively louder but they could not see the airplane. On the fifth pass, the airplane was seen approximately 50 feet above the ground and it barely cleared a stand of trees. Recorded ATC transscripts revealed that the pilot contacted approach control and told the controller that he was caught in heavy fog and wanted vectors back to the airport. The airplane crashed shortly thereafter in a snow-covered field.

An examination of the airplane showed impact damage consistent with having descended to the ground in an uncontrolled spin. An examination of the airplane's systems showed no anomalies.

Although the pilot was instrument rated, he had not flown with instruments since receiving his rating 2 years ago. He had logged 1.8 hours in actual instrument meteorological conditions, 50.8 in simulated IMC, and 6.7 hours in a flight simulator. Ceiling and visibility at the time of the accident was below landing minimums and was recorded as 200 feet overcast and 3/4-mile in mist. The RNAV (GPS) RWY 8 approach chart was found on the pilot’s lap. Although the airplane was IFR certified, it was not RNAV or GPS equipped. Toxicology results indicated the presence of propoxyphene, a prescription narcotic medication. The concentration present was consistent with use at a time outside of 24 hours prior to the accident and would not have caused impairment. Cellular telephone records showed that the pilot had engaged in calls and text message conversations with the passenger the night before the accident. Starting at 6:00 P.M. the night before the accident, the pilot received or made calls or text messages every hour, through midnight, until 3:12 A.M. In one conversation, the passenger told the pilot that he would be in good flying shape for the next day, and the pilot replied that he needed to get 4 hours of rest before he flew. The final outgoing call to the passenger was placed at 7:59 A.M. on the day of the accident.
Probable Cause: The pilot's decision to take off in known instrument meteorological conditions without instrument currency or recent instrument experience, which led to spatial disorientation resulting in an inadvertent spin. Contributing to the accident was the pilot's lack of adequate rest prior to the flight.

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

Sources:

NTSB

Location

Revision history:

Date/timeContributorUpdates
17-Jan-2010 14:21 RobertMB Added
17-Jan-2010 21:22 Geno Updated [Registration, Cn, Operator, Other fatalities, Source]
17-Jan-2010 22:54 RobertMB Updated [Aircraft type]
21-Dec-2016 19:25 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
26-Nov-2017 15:19 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:

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