ASN Wikibase Occurrence # 138926
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 2 October 2011 |
| Time: | 20:45 |
| Type: |  Piper PA-32R-300 Lance |
| Owner/operator: | Wings R Us |
| Registration: | N115CL |
| MSN: | 32R-7780439 |
| Year of manufacture: | 1977 |
| Total airframe hrs: | 4541 hours |
| Engine model: | Lycoming IO-540-K1G5D |
| Fatalities: | Fatalities: 3 / Occupants: 3 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Near Peru, about 15 miles south of Moorefield, Hardy County, WV -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Danville, VA (DAN) |
| Johnstown, PA (JST) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The non-instrument-rated pilot, who was also the owner of the airplane, departed on a night visual flight rules (VFR) flight. Weather conditions at the departure airport were VFR, the weather conditions en route were a combination of marginal VFR and instrument flight rules (IFR), and the weather at the destination airport was IFR. The pilot had obtained a weather briefing earlier in the evening, during which he was informed that VFR flight was not recommended. About 30 minutes before the accident, the pilot's in-flight weather briefing indicated that instrument meteorological conditions, including low ceilings and mountain obscuration, were forecast for their intended route and at their destination. About 4 minutes before the accident, the pilot advised air traffic control personnel that "we are losing VFR, I need a deviation." Radio and radar contact were then lost.
A postaccident examination of the wreckage indicated that the airplane struck the top of a tree, rolled inverted, and impacted the ground. No preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation were noted. The only navigational charts found at the accident scene were folded VFR charts and airport facility directories. No IFR charts were found.
Analysis of the radar data and wreckage information revealed that the airplane made a series of erratic maneuvers, including a 360-degree heading change, before entering a descent and impacting the ground at high speed. These maneuvers took place in the last few minutes of the flight and were consistent with spatial disorientation. FAA guidance indicates that spatial disorientation can occur when there is no natural horizon or surface reference, such as a night flight in sparsely populated areas similar to that of the accident area and conditions. Although about 34 percent of the moon's disk was potentially illuminated at the time of the accident, given the cloud coverage in the area it is unlikely that the moon provided any illumination over the accident site. FAA guidance also indicates that spatial disorientation is more likely to occur if a pilot lacks proficiency in instrument flying.
Probable Cause: The non-instrument rated pilot's improper decision to continue visual flight into instrument meteorological conditions, which resulted in spatial disorientation and subsequent in-flight collision with mountainous terrain.
Accident investigation:
 |
|
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 03-Oct-2011 15:13 | RobertMB | Added |
| 04-Oct-2011 10:19 | Dr. John Smith | Updated [Location, Source, Embed code, Narrative] |
| 04-Oct-2011 23:46 | ensminger | Updated [[Location, Source, Embed code, Narrative]] |
| 04-Oct-2011 23:48 | Anon. | Updated [Narrative] |
| 05-Oct-2011 07:20 | RobertMB | Updated [Time, Source, Narrative] |
| 07-Oct-2011 00:09 | David_W | Updated [Location, Source] |
| 07-Oct-2011 04:25 | RobertMB | Updated [Location, Source, Damage, Narrative] |
| 07-Oct-2011 08:24 | RobertMB | Updated [Narrative] |
| 21-Dec-2016 19:26 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 27-Nov-2017 17:21 | 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