ASN Wikibase Occurrence # 174264
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: | Wednesday 4 March 2015 |
| Time: | 04:13 |
| Type: |  Mooney M20F Executive 21 |
| Owner/operator: | Private |
| Registration: | N66BB |
| MSN: | 22-1253 |
| Year of manufacture: | 1975 |
| Total airframe hrs: | 948 hours |
| Engine model: | Lycoming IO-360A1A |
| Fatalities: | Fatalities: 3 / Occupants: 3 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Norfolk Botanical Gardens, Norfolk, VA -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Palatka, FL (28J) |
| Suffolk, VA (SFQ) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
In preparation for the night cross-country flight from southern Florida to Virginia, the private pilot contacted flight service to file instrument flight rules (IFR) flight plans for each of the two planned legs. The pilot was advised that instrument meteorological conditions (IMC), moderate turbulence, and possible low-level wind shear would prevail for the second leg of the trip (the accident flight). Although the pilot indicated to the briefer that he was aware of these conditions, the extent to which he had familiarized himself with the forecast weather could not be determined because there was no record of a complete weather briefing from an official, access-controlled source.
The first leg of the flight departed about 2030 and landed uneventfully about 2240. After obtaining fuel, the pilot and his two passengers departed on the accident flight about 2353. The airplane reached the destination airport about 0300. The airport was under low IFR weather conditions, and the pilot requested an RNAV GPS instrument approach, even though the airplane was only equipped with a handheld GPS receiver. During the approach, the air traffic controller twice noted that the pilot was having difficulty maintaining alignment with the final approach course. When asked about this by the controller, the pilot first attributed the issue to problems displaying the instrument approach charts on his GPS receiver and second to the wind correction angle necessary to hold the course. At the conclusion of the unsuccessful approach, the pilot failed to comply with the published missed approach procedure and descended to an estimated 100 ft above ground level (agl) before subsequently climbing. When asked by the controller to fly the published missed approach procedure, the pilot responded that he was unable to do so because he was “off course.”
With the assistance of air traffic controllers, the pilot diverted to a nearby airport equipped with an instrument landing system (ILS) even though similar weather conditions prevailed. The pilot was provided radar vectors for an ILS approach, but he again had difficulty maintaining the approach’s prescribed altitudes and courses, and the controller cancelled the approach clearance. About 0400, during the pilot’s second attempted approach to the diversion airport, the airplane descended to within 1 mile of the runway and about 200 ft agl. About that time, the pilot reported that he had the airport in sight, consistent with the airplane descending below the cloud ceiling. A plot of the airplane’s GPS-derived ground track and the recorded air traffic control radio transmissions showed that, about the time the pilot reported the airport in sight, the airplane was about 1/4 mile offset from the localizer but tracking toward the runway. However, instead of continuing its track toward the runway, moments later, the airplane made an abrupt, 90-degree right turn before turning left back toward the approach runway several seconds later. During the final 9 seconds of the flight, the airplane descended at a calculated descent rate of 900 ft per minute to ground impact. The airplane’s maneuvering and its final descent occurred over a relatively unlit area of water and forest. The diminished lighting conditions likely provided the pilot with limited external cues to draw from in his attempt to maintain control of the airplane and complete the visual portion of the landing approach.
Postaccident examination of the airframe and engine revealed no evidence of any preimpact mechanical malfunctions or failures. A technical performance assessment of the diversion airport’s ILS equipment revealed no discrepancies associated with the systems in use by the pilot during the attempted approach.
Throughout the approaches to both airports, the pilot repeatedly described the extreme nature of the turbulence and the high wind velocity that the airplane was encountering. Forecast and observed weather were consistent with this assessment. The pilot also described that he was having difficulty maintaining a heading due to precession
Probable Cause: The pilot's failure to properly execute the instrument approach procedure. Contributing to the accident were the pilot's improper preflight planning and his decision to conduct the flight in instrument meteorological conditions at night into forecast moderate turbulence and with inadequate avionics equipment for the planned flight.
Accident investigation:
 |
|
Sources:
NTSB
https://flightaware.com/live/flight/N66BB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 04-Mar-2015 12:53 | gerard57 | Added |
| 04-Mar-2015 13:00 | gerard57 | Updated [Location, Phase, Source, Damage, Narrative] |
| 04-Mar-2015 15:40 | gerard57 | Updated [Total fatalities, Total occupants, Source, Narrative] |
| 04-Mar-2015 17:09 | gerard57 | Updated [Total fatalities, Total occupants, Source, Narrative] |
| 04-Mar-2015 17:17 | Geno | Updated [Aircraft type, Registration, Cn, Total fatalities, Location, Departure airport, Destination airport, Source, Narrative] |
| 04-Mar-2015 17:18 | Geno | Updated [Total fatalities] |
| 04-Mar-2015 18:54 | Geno | Updated [Source, Damage] |
| 26-Mar-2015 17:14 | Geno | Updated [Time, Source, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 01-Apr-2017 10:41 | Aerossurance | Updated [Time, Location, Narrative] |
| 19-Aug-2017 14:01 | ASN Update Bot | Updated [Time, 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