ASN Wikibase Occurrence # 163786
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: | Friday 7 February 2014 |
| Time: | 19:30 |
| Type: |  Piper PA-28-161 Warrior II |
| Owner/operator: | Fishe Flying Corp |
| Registration: | N2571U |
| MSN: | 28-8016037 |
| Year of manufacture: | 1979 |
| Engine model: | Lycoming O-320 |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Atlantic Ocean, St. Lucie Inlet, off the coast of Stuart, Florida -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Marathon, FL (MTH) |
| Vero Beach, FL (VRB) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
According to the operator/owner, the noninstrument-rated pilot was visiting the United States on vacation and had rented the airplane for about 1 week. The pilot planned a day trip to an airport located about 2.5 hours from the airplane’s home base, and the accident occurred on the return leg. After departing on the return leg, the pilot contacted air traffic control and requested flight-following services for the planned flight route, which was just offshore of the southeastern coast of Florida. About 1.5 hours into the flight and almost 1 hour after sunset, the accident pilot heard another pilot, who was operating on the same radio frequency, request an instrument flight rules clearance to an airport that was between the accident pilot’s position and his intended destination. The accident pilot then requested an update of the current weather conditions at his destination, and an air traffic controller advised that an overcast ceiling of 600 ft prevailed. When the pilot requested the weather conditions for a slightly closer airport, the controller advised that there were scattered clouds at 700 ft and an overcast ceiling at 1,000 ft. The pilot subsequently advised the controller that he intended to divert the flight to the closer airport.
As the flight continued, the pilot discussed the weather conditions with an air traffic controller, noting that the cloud ceiling was “pretty low” and that he couldn’t “get a real handle on the ceiling.” The controller then asked the pilot what altitude he could maintain, and he responded “700 ft.” After transitioning to an area without low-altitude radar coverage, the pilot advised that he was flying at an altitude of 450 ft. An air traffic controller then advised the pilot that flight-following services were not available at that altitude, and, after flight-following services were terminated, no further radio communications were received from the pilot.
The operator reported the airplane missing when it did not return later that evening as scheduled, and personal effects and airplane wreckage began washing ashore the following morning in the vicinity of the flight’s last known position. No radar coverage was available in the area where the accident likely occurred; therefore, the exact sequence of events that resulted in the airplane’s ultimate impact with water could not be determined. However, the condition of the recovered wreckage was consistent with water impact at a significant velocity.
The weather forecast at the pilot’s original destination airport at the time of his departure indicated that marginal visual meteorological conditions (VMC) would prevail at the time of his anticipated arrival. As the flight progressed, the conditions en route and at the destination eventually deteriorated below VMC, and, as noted, the pilot discussed the deteriorating weather conditions with the air traffic controller several times. Although the reported visibilities in the area were favorable, the flight was conducted on a dark, moonless night under an overcast ceiling, over the ocean, and off a relatively sparsely populated area of the coast. These factors would have reduced the pilot’s ability to perceive the natural horizon and increased his risk of losing airplane control due to spatial disorientation. The pilot might have reduced this risk by diverting the flight earlier to a destination with more favorable weather and lighting conditions. However, the pilot ultimately chose to divert to an airport that was only slightly closer than his original destination, which reported weather conditions at visual flight rules minimums. At the time of the actual diversion, the airplane was passing within 4 nautical miles of a large international airport, which at the time was reporting a cloud ceiling higher than 4,000 ft. Even after this point, the pilot could have chosen to turn around and return to this airport rather than continuing the flight into deteriorating conditions.
Probable Cause: The noninstrument-rated pilot’s continued flight into dark night, instrument meteorological conditions, which resulted in a loss of control due to spatial disorientation and subsequent impact with water.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=2571U
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 10-Feb-2014 21:29 | gerard57 | Added |
| 13-Feb-2014 04:36 | Geno | Updated [Aircraft type, Operator, Location, Departure airport, Destination airport, Source, Narrative] |
| 19-Feb-2014 19:33 | Geno | Updated [Aircraft type, Registration, Cn, Source] |
| 06-Mar-2014 22:34 | Geno | Updated [Time, Location, Source, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 29-Nov-2017 13:33 | ASN Update Bot | Updated [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