Beechcraft A36 N999PK
28 May 2013 · Mountainaire, Arizona, United States · Fatal
Summary
On 28 May 2013 at about 18:43 local time, a Beechcraft A36 registered N999PK was involved in an accident near Mountainaire, Arizona, United States. 2 people were on board and 2 died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 18:43
- Classification
- Accident
- Location
- Mountainaire, Arizona, United States
- Nearest airport
- Flagstaff Pulliam Airport (FLG)
- Coordinates
- 35.0828, -111.6678
- Aircraft
- Beechcraft A36
- Registration
- N999PK
- Category
- Airplane
- Year built
- 2001
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Flagstaff → Bryce Canyon
- Aircraft damage
- Destroyed
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR13FA244
People
2 people died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 2 | 0 | 0 | 0 |
Probable cause
The pilot's inability to maintain a climb after departure in high-density altitude conditions, which resulted in a collision with trees and terrain. Contributing to the accident were the pilot's decision not to track the four-lane highway just beyond the departure runway, which he could have used as an alternate landing site; his premature rotation of the airplane; and degraded engine performance that affected the airplane's climb ability.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The pilot had purchased the Beechcraft airplane about 18 months before the accident and based it at his home airport, which was located at an elevation of about 80 ft mean sea level (msl). The pilot flew the Beechcraft to an airport that was at an elevation of about 7,100 ft msl. A few days after his arrival, he returned to the airport for his planned departure and spent about 15 minutes asking the fixed base operator owner, who was also a pilot, multiple questions about the route to his next planned destination. According to the owner, he was surprised by the nature of the pilot's questions, his lack of basic aeronautical information knowledge for area restrictions, and his lack of formal planning for his flight. No witnesses reported anything unusual about the engine start or taxi. At the time the pilot was cleared by the air traffic control tower controller for takeoff, the airport density altitude was about 9,000 ft. No ground witnesses reported observing anything unusual with the takeoff, but a Cessna 172 pilot who was behind the Beechcraft reported that the Beechcraft's climbout was slow. Shortly after his own takeoff, about 75 seconds after the Beechcraft, the Cessna pilot asked the tower controller about the Beechcraft's situation and intentions because the Cessna was already well above the Beechcraft. This prompted the controller to ask the Beechcraft pilot if he needed assistance, and the pilot responded that he was climbing "very slowly" and would remain near the airport. Shortly after that, the Cessna pilot saw the Beechcraft impact trees. The accident site was about 3 miles southeast of the airport at an elevation about 300 ft below that of the departure airport. A postimpact fire obscured or destroyed a significant amount of evidence. Review of the Beechcraft's published performance data revealed that, for the given conditions, the airplane should have been able to successfully depart the airport and climb at a rate of about 500 feet per minute. Most of the engine components and all of the propeller components that survived the accident, displayed no evidence of preimpact mechanical deficiencies. The engine cylinder conditions were indicative of a history of generally lean operation. In addition, the No. 5 cylinder exhaust valve's appearance was consistent with excessively lean operation for an undetermined period of time, and the fuel injector nozzle for that cylinder was found to be partially occluded. Excessively lean operation will reduce engine power output, and will manifest itself as abnormally high exhaust and cylinder head temperatures and possible engine roughness. Further, if the No. 5 cylinder's injector was occluded for the flight, it would have resulted in overly lean operation of and reduced power output from that cylinder, yielded higher exhaust and cylinder head temperatures, and likely manifested itself as engine roughness. (Some witnesses close to the impact site reported that the engine was making "popping" noises.) Although the airplane was equipped to monitor, display, and record temperatures for each cylinder, it could not be determined whether the pilot monitored that display, and fire damage prevented the recovery of that data from the engine monitor. Further, there was insufficient evidence to determine the source of the injector's occlusion, quantify its effects on engine power output, determine its relation to the condition of the exhaust valve, or determine if it was present for the takeoff or an artifact of the postimpact fire. Although the engine was developing power at impact, there was insufficient evidence to quantify the actual power output for the climb or at the time of impact. There was also insufficient evidence to determine whether the pilot ensured that the throttle and propeller controls were set to and remained in their appropriate positions for the departure or whether the pilot adjusted the mixture properly (not overly lean). It is likely that the pilot lifted off prematurely at a speed lower than the prescribed value and was unable to accelerate or climb the airplane once it exited the ground effect regime. Because the surrounding terrain and the impact point were lower than the elevation of the airport, the pilot was able to continue to fly the airplane before crashing. This scenario is at least partially corroborated by the pilot's reported lack of preparation for the flight, which could have included a lack of performance planning. This scenario is also partially corroborated by the observed repetitive minor banking of the airplane, which often occurs when an airplane is flying very slowly. A premature liftoff or a climb attempt at a speed significantly below the prescribed value would place the airplane in a situation where the power required for level flight was very near to or exceeded the available power. A recovery would require the pilot to lower the nose in order to accelerate the airplane to obtain a positive rate of climb. Such an action is counterintuitive when low to the ground and requires accurate problem recognition, knowledge of the correct solution, and sufficient terrain clearance to accomplish. During the departure, the pilot reduced his options by deciding to turn to the east instead of continuing straight ahead to the south. Review of topographic data revealed that a four-lane highway was located just beyond the south end of the runway, and was situated in a north-south valley that descended to the south. However, instead of tracking over that highway, which could have been used as an off-airport emergency landing site, and its descending valley, which provided increasing terrain clearance, the pilot opted to turn east, toward higher, wooded terrain. Although that turn was consistent with both a left traffic pattern (in order to remain close to the airport as the pilot reported to the air traffic controller), and toward the pilot's on-course heading, by making that turn, the pilot reduced the likelihood of a partially or fully successful outcome to the flight.
Quoted verbatim from the NTSB record.
Other Beechcraft A36 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 15 Apr 2013 | Beechcraft A36 | Port Alsworth, Alaska, United States | Lake Clark Air, INC | No injuries | - |
| 1 May 2013 | Beechcraft A36 | Ingalls, Indiana, United States | WV Aviation LLC | No injuries | - |
| 4 Aug 2013 | Beechcraft A36 | Alma, Georgia, United States | APS Aviation LLC | Fatal | 2 |
| 18 Aug 2013 | Beechcraft A36-TC | Ami, Japan | - | Serious injuries | - |
| 23 Sep 2013 | Beechcraft A36 | Wellington, Florida, United States | Fourstars Aviation | No injuries | - |
| 6 Oct 2013 | Beechcraft A36 | Tilden, Texas, United States | J & J Aircraft LLC | Serious injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 19 Apr 2013 | CubCrafters CC11-160 | Mesa, Arizona, United States | - | No injuries | - |
| 20 Apr 2013 | Hoffman RV-4 | Bullhead City, Arizona, United States | - | Fatal | 1 |
| 8 Jun 2013 | Eurocopter EC 130 B4 | Grand Canyon, Arizona, United States | Papillon Grand Canyon Helicopters | No injuries | - |
| 2 Nov 2013 | Rovey Jason H RV-8 | Wickenburg, Arizona, United States | - | No injuries | - |
| 23 Apr 2013 | Bell 206L-1 | Grand Canyon, Arizona, United States | Papillon Airways Inc | No injuries | - |
| 7 Nov 2013 | Piper PA 46 350P | Carefree, Arizona, United States | - | No injuries | - |