ASN Wikibase Occurrence # 21513
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 27 June 2008 |
| Time: | 03:41 |
| Type: |  Eurocopter AS 350B3 Squirrel |
| Owner/operator: | Phi Incorporated |
| Registration: | N586AE |
| MSN: | 3725 |
| Year of manufacture: | 2003 |
| Total airframe hrs: | 1521 hours |
| Engine model: | Turbomeca Arriel 2B |
| Fatalities: | Fatalities: 0 / Occupants: 3 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | 2 miles west of Ash Fork, Arizona -
 United States of America
|
| Phase: | Landing |
| Nature: | Ferry/positioning |
| Departure airport: | Prescott, AZ (PRC) |
| Ash Fork, AZ | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The helicopter pilot was dispatched to a highway motorcycle accident on the night flight. The pilot reported that he was wearing night vision goggles and that the weather en route was clear skies with unrestricted visibility. As he approached the vehicle accident location he contacted the incident commander by radio and was instructed to land at a landing zone (LZ) about 1.5 miles north of the vehicle accident location. The pilot performed an orbit around the vehicle accident site and determined that it would be safe for him to land there directly. He once again contacted the incident commander and requested to land but the incident commander instructed the pilot to continue north to the LZ. Upon arrival at the LZ, the pilot reconnoitered the site and observed that the incident commanders' vehicle was situated in a location that would make the approach for landing steeper than normal. He therefore elected to change the approach to a route that would take him over a sparsely vegetated dirt field, followed by a gravel road, and then a paved road for the final approach to touchdown. Halfway through the approach the flight encountered brownout conditions and he began to perform a go-around. He reported being confident that he had initiated a climb, but shortly thereafter the helicopter impacted the ground. During the impact sequence the helicopter rolled on its right, and the main rotor, tail rotor, and engine separated from the fuselage. The pilot stated that the helicopter and engine had no mechanical failures or malfunctions during the flight.
Probable Cause: The pilot's spatial disorientation resulting in his failure to detect and compensate for an unintentional descent during a go-around. Contributing to the accident were the pilot's inadequate choice of landing approach, reduced visibility from brownout conditions, and the dark night.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?omni=Home-N-Number&nNumberTxt=N586AE
Location
Media:
 |
| Photo Courtesy of FlightAware.com |
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 29-Jun-2008 21:42 | Fusko | Added |
| 12-Jul-2008 12:25 | Fusko | Updated |
| 11-Jun-2010 02:28 | TB | Updated [Operator, Source, Narrative] |
| 25-Jul-2012 12:16 | flagrn | Updated [Total occupants, Source, Narrative] |
| 18-Jul-2014 18:44 | Dr. John Smith | Updated [Operator, Location, Departure airport, Destination airport, Source, Embed code, Narrative] |
| 21-Dec-2016 19:14 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 21-Dec-2016 19:16 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 21-Dec-2016 19:20 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 03-Dec-2017 11:18 | ASN Update Bot | Updated [Operator, Other fatalities, Nature, 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