ASN Wikibase Occurrence # 192339
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: | Tuesday 27 December 2016 |
Time: | 17:56 |
Type: | Epic LT |
Owner/operator: | Private |
Registration: | N669WR |
MSN: | 029 |
Year of manufacture: | 2009 |
Total airframe hrs: | 822 hours |
Engine model: | P&W Canada PT6A-67A |
Fatalities: | Fatalities: 2 / Occupants: 2 |
Aircraft damage: | Substantial |
Category: | Accident |
Location: | Spruce Creek Airport (7FL6), Daytona Beach, FL -
United States of America
|
Phase: | Landing |
Nature: | Private |
Departure airport: | Millington, TN (NQA) |
Destination airport: | Port Orange, FL (7FL6) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:The private pilot obtained a full weather briefing before departing on a long cross-country flight. The destination airport was forecast to be under visual meteorological conditions, but there was an AIRMET and Center Weather Advisory (CWA) issued for low instrument flight rules (IFR) conditions later that day. The briefer told the pilot to check the weather again en route to see if the AIRMET and CWA had been updated. At the time the pilot stopped for fuel, another CWA was issued for low IFR conditions at his destination airport; however, there were no records to indicate that the pilot obtained this information during the fuel stop or after departing on the last leg of the flight.
A review of air traffic control communications revealed that, about 10 minutes before arriving at the airport, the pilot reported that he had obtained the current weather conditions at his destination airport. The most recent observation, about 1 hour before the accident indicated good visibility; however, the weather reporting equipment did not provide ceiling heights. It is unknown if the pilot obtained weather information from nearby airports, which were reporting low instrument meteorological conditions (visibility between 1/4 and 1/2 mile and ceilings 200-300 ft above ground level [agl]). Additionally, three pilot reports (PIREPs) describing the poor weather conditions were filed within the hour before the accident. The controller did not relay the PIREPs or the CWA information to the pilot, so the pilot was likely unaware of the deteriorating conditions.
Based on radar information and statements from witnesses, the pilot's approach to the airport was unstabilized. He descended below the minimum descent altitude of 440 ft, and, after breaking through the fog about 100 ft agl, the airplane reentered the fog and completed a 360° right turn near the approach end of the runway, during which its altitude varied from 100 ft to 300 ft. The airplane then climbed to an altitude about 800 ft before radar contact was lost near the accident site. The airplane came to rest inverted, consistent with one witness's statement that it descended through the clouds in a spin before impact; postaccident examination revealed no preimpact anomalies with the airplane or engine that would have precluded normal operation. Although the pilot was instrument rated, his recent instrument experience could not be established.
The circumstances of the accident, including the restricted visibility conditions and the pilot's maneuvering of the airplane before the impact, are consistent with a spatial disorientation event. It is likely that the pilot experienced a loss of control due to spatial disorientation, which resulted in an aerodynamic stall and spin.
Probable Cause: The pilot's loss of airplane control due to spatial disorientation, which resulted in the exceedance of the airplane's critical angle of attack and an aerodynamic stall/spin. Contributing to the accident was the pilot's failure to fly a stabilized approach consistent with the published instrument approach procedure.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | ERA17FA074 |
Status: | Investigation completed |
Duration: | 1 year and 6 months |
Download report: | Final report |
|
Sources:
NTSB
FAA register:
http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?nNumberTxt=669WR Location
Images:
Photo: NTSB
Revision history:
Date/time | Contributor | Updates |
28-Dec-2016 02:00 |
Geno |
Added |
28-Dec-2016 02:15 |
Geno |
Updated [Registration, Cn, Operator, Departure airport, Source, Narrative] |
28-Dec-2016 08:04 |
harro |
Updated [Embed code] |
22-Jul-2018 18:50 |
ASN Update Bot |
Updated [Time, Operator, Nature, Departure airport, Destination airport, Source, Embed code, Narrative] |
22-Jul-2018 19:38 |
harro |
Updated [Source, Embed code, Narrative, Photo, ] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation