ASN Wikibase Occurrence # 142269
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 3 February 2012 |
| Time: | 08:56 |
| Type: | Lancair Propjet |
| Owner/operator: | Private |
| Registration: | N321LC |
| MSN: | 003 |
| Year of manufacture: | 2003 |
| Total airframe hrs: | 339 hours |
| Engine model: | Diemech Turbine M601D |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Boise Airport, Boise, ID -
 United States of America
|
| Phase: | Initial climb |
| Nature: | Private |
| Departure airport: | Boise Airport, ID (BOI/KBOI) |
| Boise Airport, ID (BOI/KBOI) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The amateur-built, experimental, high-performance airplane was fueled to capacity and the pilot had planned a cross-country flight. During an initial takeoff, the airplane climbed to about 60 feet above ground level (agl) before touching back down; the pilot transmitted to the air traffic controller that he had a problem. The controller asked if the pilot needed any assistance, and the pilot responded that he was going to taxi back and "see if I can figure it out," indicating that there was not a catastrophic failure and the pilot was intending to troubleshoot the problem. The pilot then taxied to a ramp area where the airplane was stationary for almost a minute and a half. Although the pilot's actions during this period are not known, it is likely that he was attempting to troubleshoot a problem with the airplane because the recorded engine parameters are consistent with the pilot cycling the propeller.
Thereafter, the pilot stated his intention to stay in the traffic pattern, and he taxied the airplane back to the runway. The airplane became airborne about 18 seconds into the takeoff; the pilot then made a request to turn back to land. The airplane turned to the left and continued to climb until it reached its peak altitude of about 320 feet agl. Witnesses indicated that the airplane then entered a spin, completed about one revolution, and impacted terrain in a nose-low attitude before coming to rest in a dirt area between the parallel runways. A fire started upon impact.
At the peak of the airborne portion of the first rejected takeoff, about 5,860 feet of runway remained. When the pilot made the request to turn back to land during the second takeoff, over 5,160 feet of runway remained, but because the airplane was 260 feet higher and had a higher airspeed than previously, the pilot likely thought he would not be able to land on the runway surface straight ahead. A performance study indicated that the airplane experienced a loss of thrust during the accident takeoff about 1 second before the pilot's request to return.
Postaccident examination revealed no evidence of a preimpact uncontained engine failure, inflight fire, or flight control system malfunction. Fuel system continuity could not be confirmed due to thermal damage incurred during the postcrash fire. Review of the engine parameters revealed that, during the accident takeoff, the greatest anomaly in the airplane's parameters was that the fuel pressure dropped to a minimum psi while the fuel flow increased and the torque delivered to the engine shaft (Q) increased excessively. Shortly thereafter, fuel pressure recovered when the fuel flow reduced and Q retarded to an idle setting. Q also dropped to an idle setting during the previous takeoff. The reason for these variations could not be explained. In comparing prior flights to the accident flight, the maximum Q attained during takeoff climb was lower than the Q for the accident takeoff, and the fuel pressure did not drop to the same level as during the accident flight, which are indicative of a problem with the airplane.
The airplane was equipped with a Turbine Starter Limiting/Monitoring System, capable of limiting power by restricting fuel flow, which was designed to act as a start sequence controller, an engine protection limiter, and an engine monitor/recorder. It is possible that this system/installation malfunctioned and engaged during the accident takeoff; however, the system was destroyed in the postcrash fire and could not be examined. Consequently, no determination regarding its performance during the accident flight is possible.
The data showed that the pilot's most recent flight in the airplane was 6 days before the accident, at the same airport. During that flight, he also performed an initial rejected takeoff, suggesting that he was possibly having problems at that time; he made a successful flight thereafter, but remained in the traffic pattern.
A simulation of the accident flight indicated that, during the airplane's left turn, the angle of attack at which the wing stalls
Probable Cause: A loss or commanded reduction of engine power during the initial climb for reasons that could not be determined because of postaccident impact damage and fire destruction to engine systems and components. Also causal were the pilot's failure to maintain adequate airspeed and airplane control while attempting to return to the runway despite unpopulated, flat terrain immediately ahead that was suitable for an emergency landing; his decision to take off again with a known problem; and his lack of training in the make and model airplane.
Accident investigation:
 |
|
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 03-Feb-2012 13:08 | Alpine Flight | Added |
| 03-Feb-2012 13:15 | Alpine Flight | Updated [Time, Departure airport] |
| 03-Feb-2012 14:56 | RobertMB | Updated [Time, Aircraft type, Registration, Cn, Operator, Source, Narrative] |
| 03-Feb-2012 15:00 | RobertMB | Updated [Source] |
| 06-Feb-2012 11:11 | Geno | Updated [Source] |
| 11-Feb-2012 08:32 | Dr. John Smith | Updated [Time, Location, Departure airport, Source, Narrative] |
| 09-Sep-2014 18:53 | Aerossurance | Updated [Operator, Narrative] |
| 21-Dec-2016 19:26 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 27-Nov-2017 20:18 | ASN Update Bot | Updated [Other fatalities, Departure airport, Destination airport, Source, Narrative] |
| 16-Sep-2023 11:58 | Ron Averes | 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