Scottsdale, AZ, USA
N3636Q
Piper PA-60-601P
The airplane collided with mountainous terrain 5 miles from the departure airport during a dark night takeoff. Review of recorded radar data found a secondary beacon code 7267 (the code assigned to the airplane's earlier inbound arrival ) on the runway at 2021:08, with a mode C report consistent with the airport elevation. Two more secondary beacon returns were noted on/over the runway at 2021:12 and 2021:19, reporting mode C altitudes of 1,600 and 1,700 feet, respectively. Between 2021:08 and 2021:38, the secondary beacon target (still on code 7267) proceeded on a northeasterly heading of 035 degrees (runway heading) as the mode C reported altitude climbed to 2,000 feet and the computed ground speed increased to 120 knots. Between 2021:38 and 2021:52, the heading changed from an average 035 to 055 degrees as the mode C reports continued to climb at a mathematically derived 1,300 feet per minute and the ground speed increased to average of 170 knots. At 2022:23, the code 7267 target disappeared and was replaced by a 1200 code target. The mode C reports continued to climb at a mathematically derived rate of 1,200 feet per minute as the ground speed increased to the 180-knot average range. The computed average heading of 055 degrees was maintained until the last target return at 2022:53, which showed a mode C reported altitude of 3,500 feet. The accident site elevation was 3,710 feet and was 0.1 miles from the last target return. The direct point to point magnetic course between Scottsdale and Santa Fe was found to be 055 degrees. Numerous ground witnesses living at the base of the mountain where the accident occurred reported hearing the airplane and observing the aircraft's lights. The witnesses reported observations consistent with the airplane beginning a right turn when a large fireball erupted coincident with the airplane's collision with the mountain. No preimpact mechanical malfunctions or failures were found during an examination of the wreckage. The radar data establishes that the pilot changed the transponder code from his arrival IFR assignment to the VFR code 30 seconds before impact and this may have been a distraction.
1.1 History of Flight On January 26, 2003, at 2023 mountain standard time, a Piper PA-60-601P, N3636Q, collided with mountainous terrain after takeoff from the Scottsdale, Arizona, airport. The airplane was owned and operated by the pilot under the provisions of 14 CFR Part 91 of the Federal Aviation Regulations. The airplane was destroyed in the impact and post crash fire sequence. The instrument rated private pilot and one passenger sustained fatal injuries. Night visual meteorological conditions prevailed with unrestricted visibility; however, the moon was not above the horizon. No flight plan was filed for the personal cross-country flight that originated in San Diego, California, at 1500 Pacific standard time as a flight to Santa Fe, New Mexico, with a planned stop in Scottsdale. According to a Safety Board Sun and Moon location program for the geographic coordinates and altitude of Scottsdale, sunset occurred at 1758, and nautical twilight ended at 1854. At the time of the accident, the moon was 75 degrees below the northeastern horizon. Information was obtained from the following Federal Aviation Administration (FAA) facilities: Western Pacific Air Traffic Quality Assurance Division, San Diego Automated Flight Service Station (AFSS), Phoenix Terminal Radar Approach Control (PHX TRACON), and Scottsdale Air Traffic Control Tower (ATCT). The pilot requested and received a preflight weather briefing for the flight from San Diego AFSS and filed an instrument flight rules flight plan from San Diego to Scottsdale. According to the facilities who worked the flight, the instrument arrival into Scottsdale was routine and the airplane landed at 1811. The flight's inbound assigned discrete transponder code was 7267. At 2016, the pilot contacted Scottsdale ATCT clearance delivery and requested VFR flight following to Santa Fe. The controller denied the pilot's request and advised him to contact Phoenix TRACON after he was airborne. The pilot contacted ground control at 2017, advising that he was ready to taxi for takeoff, and the flight was cleared to runway 03. At 2020, the pilot advised the local controller that he was ready for takeoff and asked for a right turn. The controller then cleared the flight for takeoff. Recorded radar data from the FAA's Phoenix Terminal Radar Approach Control (TRACON) ARTS IIIA radar system was obtained and reviewed. At 2021:08, a secondary beacon code 7267 was observed on the runway at the Scottsdale airport with a mode C report of 1,500 feet. Two more secondary beacon returns were noted on/over the runway at 21:12 and 21:19, reporting mode C altitudes of 1,600 and 1,700 feet respectively. Between 21:08 and 21:38, the secondary beacon target (still on code 7267) proceeded on a northeasterly heading computed by the ARTS IIIA system of 035 degrees as the mode C reported altitude climbed to 2,000 feet and the computed ground speed increased to 120 knots. Between 21:38 and 21:52, the computed heading changed from an average 035 to 055 degrees as the mode C reports continued to climb at a mathematically derived 1,300 feet per minute and the ground speed increased to average of 170 knots. At 22:23, the code 7267 target disappeared and was replaced by a 1200 code target. The mode C reports continued to climb at a mathematically derived rate of 1,200 feet per minute as the ground speed increased to the 180-knot average range. The computed average heading of 055 degrees was maintained until the last target return at 22:53, which showed a mode C reported altitude of 3,500 feet. The accident site elevation was 3,710 feet and was 0.1 miles from the last target return. The direct point-to-point magnetic course between Scottsdale and Santa Fe was found to be 055 degrees. Numerous ground witnesses living at the base of the mountain where the accident occurred reported hearing the airplane and observing the aircraft's lights. The witnesses reported observations consistent with the airplane beginning a right turn when a large fireball erupted coincident with the airplane's collision with the mountain. 1.2 Pilot Information Review of the FAA airman and medical certification files disclosed that the pilot held a private pilot certificate with airplane ratings for single engine land, multiengine land and instruments. The most recent issuance of his certificate was dated May 2, 2000. A second-class medical certificate was issued to the pilot on May 3, 2002, and contained the limitation that correcting lenses be worn and that glasses for near and intermediate vision be carried. The pilot's personal flight records were not recovered. On the May 3, 2002 application for his medical certificate, the pilot listed his total flight time as 1,450 hours. On an application for insurance coverage dated July 2, 2001, the pilot reported a total time of 1,400 hours, with 160 accrued in the accident airplane. Contained in the insurance file was a certificate that showed the pilot had completed ground and flight recurrency training in the accident airplane on August 9, 2001. 1.3 Aircraft Information The aircraft, a Piper PA-60-601P, serial number 61P07858063398, was manufactured in 1980. The maintenance logbooks for the aircraft, engines, and propellers were not located. The investigation obtained and reviewed a certified copy of the registration and airworthiness files maintained by the FAA Civil Aircraft Registry office in Oklahoma City, Oklahoma. In addition, the investigation was able to identify an aircraft maintenance shop in Brigham City, Utah, that performed maintenance on the aircraft, and copies of the recent work orders for maintenance performed were obtained. With these sources, the maintenance and modification history of the airplane was partially reconstructed. In 1996 the aircraft was acquired by the Machen Corporation and several modifications were performed under FAA approved Supplemental Type Certificates to convert the airplane to what is popularly known as a "Machen conversion." In pertinent part, the modifications included the removal of the original 290-horsepower Lycoming IO-540-S1A5 engines and installation of Lycoming TSIO-540-U2A engines that develop 350 horsepower. The Aerostar Corporation acquired the airplane in 1998 and used the airplane as a factory demonstrator and test bed for various avionic system approvals by the FAA. During this time, a Bendix-King KFC255 auto pilot and flight director system was installed. Other modifications performed at various times included the installation of a fuselage mounted auxiliary fuel tank and a GPS navigation system. The GPS system was approved for navigation in VFR and IFR conditions in the en route, terminal, and approach environments. The steering signal output of the GPS was channeled to the horizontal situation indicator (HSI). The last work order from The Flight Shop, Inc., Brigham City, Utah, was dated June 21, 2002, and listed the completion of an annual inspection. The total time on the airframe at the time of the annual was 2,574 hours. According to the firm's personnel, at the time of the annual a complete Airworthiness directive (AD) listing was performed, with all AD's applicable to the airplanes serial number accomplished. Based on references in the FAA airworthiness files, the engines and propellers are estimated to have accrued between 800 and 900 hours since installation in the airframe. No information was available to determine the overhaul status of the engines. The airplane was parked at a FBO on the Scottsdale airport for 2 hours following the flight's arrival at 1811. Interviews with ground service personnel at the Scottsdale FBO where the airplane was parked revealed that no services were provided. Review of a FAA approved Pilot Operating Handbook for a Piper PA-60-601P applicable to the serial number of the accident airplane disclosed that at the ambient atmospheric conditions existing at the time of takeoff, the airplane would have had a typical climb rate of 1,500 feet per minute. 1.4 Meteorological Information The weather observation taken at the Scottsdale airport at 2053 listed clear skies with a 10 mile visibility; winds from 010 at 3 knots; and an altimeter setting of 30.17 inches of mercury. A Safety Board computer program was used to calculate the position of the sun and moon at the time of the accident. Sunset occurred at 1756, with the end of astronomical twilight at 1922. At 2023, the sun was 30 degrees below the western horizon. The moon was 75 degrees below the northeastern horizon. There are no ground lights on the eastern side of the McDowell mountains that the airplane collided with which would provide a source to silhouette the rising terrain. 1.5 Wreckage and Impact The accident site is located in the McDowell mountain range on the southwest facing slope of a mountain at the 3,780-foot mean sea level (msl) and about 100 feet below the ridge crest. The slope of the mountain at the site was about 60 degrees, with terrain consisting of large and small rocks of various diameters to 6 feet. Sparse scrub vegetation typical of the Arizona deserts was present widely distributed over the slope. The Scottsdale airport, elevation 1,510 feet msl, was visible about 5 miles distant on a magnetic bearing of 235 degrees. An initial upsloping ground disturbance about 12 feet wide by 20 feet long was observed on the slope on a southeast line of bearing. This disturbance was characterized as a gouge-like depression in the ground. A median path of disturbed rocks, aircraft debris, and sooted fire residue was distributed over a horizontal distance of about 200 feet, with wreckage components scattered about 30 feet upslope and 100 feet downslope of the median debris field. The farthest piece of wreckage was the right engine, which was found about 300 feet downslope of the debris field. The airplane was extensively fragmented and burned. Examination of the recovered airframe fragments disclosed that the principal vertical and horizontal crush deformation was to the lower fuselage and bottom wing skins. Following initial on-site documentation, the extensively fragmented and burned wreckage was removed from the mountain and taken to the facilities of Air Transport, Phoenix, Arizona, for detailed examination. 1.6 Tests and Research 1.6.1 Airframe Structure The Piper Corporation data plate was identified on the lower portion of the rear empennage tail cone and identified the airplane as model 601P, serial number 61P07858063398. A second data plate found near the Piper one identified the airplane as a Machen conversion, serial number 65-182, and listed Supplemental Type Certificate (STC) 1658NM. The fuselage was extensively fragmented, with the only readily identifiable pieces consisting of the approximate upper 6 feet of the cabin roof section and the aft most 5 feet of the empennage, from the horizontal leading edge aft to the end of the tail. The roof section encompassed the cabin side windows and ran from the upper forward windshield boundary to the approximate rear cabin bulkhead. The main wing spar carry through and associated bulkhead, with the inboard sections of the left and right wings, were also identifiable in the wreckage; however, they were thermally damaged. About half of the remaining wreckage fragments were exposed to thermal damage. The cabin entry door and window was identified in the debris. The cockpit/cabin entry door (located at the pilot's seating position) upper section was found fragmented and distorted. The corresponding fuselage doorframe was located in the wreckage debris. Both locking pins for the upper door were bent and distorted. The pinholes in the fuselage doorframe were ovaled and distorted on the outboard edge of the hole bores. The window latching mechanism was found in the locked position. No slip stream influenced sooting or rivet shadowing was noted. All fire damage noted on the airframe components was random in character and consistent with the debris orientation on the mountain slope. The inboard 6.5 feet of the right wing remained attached to the fuselage carry through and was moderately fire damaged. The right engine was separated from the nacelle mounts and was located downslope of the wreckage about 300 feet. The right main landing gear was visually in the down position with a corresponding position noted on the hydraulic actuator rod; however, it was noted that the entire hydraulic system had been compromised and no fluid remained in the cylinder (this system has no up locks, pressure only holds the gear in the wells). The right wing flap actuator was measured at 2 inches of extension (according to Piper technical documentation, 2.05 inches equals flaps up while 4.9 inches equals flaps 10 degrees). The right aileron was segmented into two pieces and separated from the outboard wing section. The right wing tip cap and pieces of structure encompassing the outboard wing section were identified in the recovered debris. The moderately fire damaged inboard 6.5 feet of the left wing was separated from the carry through structure and found in the debris field. The left engine remained attached to this section of the wing by its associated control cables and fluid lines. The left main landing gear assembly was separated from the structure and the landing gear hydraulic cylinder was identified with the piston rod bent and trapped at a 6.75-inch extension, which is consistent with the gear in a retracted position. The left wing flap actuator was measured at 2.25 inches of extension (according to Piper technical documentation, 2.05 inches equals flaps up while 4.9 inches equals flaps 10 degrees). The left aileron was intact but buckled in a spanwise direction and separated from the outboard wing section. The left wing tip cap and pieces of structure encompassing the outboard wing section was identified in the recovered debris. The left and right horizontal stabilizers, with elevators attached, remained secured to the empennage section. No impact damaged was observed to the right horizontal stabilizer or elevator. A chordwise pattern of thermal damage was observed on the upper skin of the right horizontal stabilizer over the outboard 24 inches, with more extensive thermal effects noted on the elevator than on the stabilizer leading edge. No thermal damage was observed on the corresponding bottom skin sections. The left horizontal stabilizer exhibited extensive leading edge crush damage. The elevator trim tab actuator was measured at 2.93 inches (according to Piper technical documentation, this equals a tab down deflection of 1/8). The vertical stabilizer and rudder separated from the empennage, with the rudder secured to the stabilizer by the hinge and hangar assemblies. The rudder trim tab actuator measured 3.0 inches of extension (according to Piper technical documentation, 3.1 inches equals neutral). 1.6.2 Engine Examinations The engines were identified as Lycoming TSIO-540-U2A, which develop 350 horsepower at 2,500 rpm. 1.6.2.1 Right Engine The right engine, serial number L-9722-61A, was not fire damaged. Cylinder Nos. 1 and 2 were impact damaged. The crankshaft flange was intact, with bending and tearing noted over a 30-degree arc through two propeller hub bolt holes. Ductile crushing was evident on the exhaust risers. The left magneto and propeller governor were missing. The mounting flange for the propeller governor remained secured to the case, with overload fractures evident. The left magneto's mounting clamps remained attached at their respective studs. Rotation of the crankshaft produced accessory gear train continuity and strong thumb compression on cylinder Nos. 1, 5, and 6. Debris was noted under the exhaust valve seats on cylinder Nos. 3 and 4. Cylinder No. 2 exhibited impact damage, with the rocker box and internal components missing. The right magneto was secure on its mounting pad with impact damage evident on the cap assembly. Hand rotation produced sparks at five of the six posts. The top spark plugs, Champion RHB-36S, were removed; no mechanical damage was noted and the electrodes and posts exhibited a light ash gr
the pilot's failure to maintain an adequate altitude clearance from mountainous terrain. Contributing factors were dark night conditions, mountainous terrain, and the pilot's diverted attention.
Source: NTSB Aviation Accident Database
Aviation Accidents App
In-Depth Access to Aviation Accident Reports
