What happened
The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.
Pilot was conducting cargo flight from holbrook AZ (P14) to phoenix, AZ (phx) with a scheduled stop in Payson AZ (pan) to pick up & deliver express packages for ups. Aircraft was seen departing holbrook airport between 4:50 ? 5:00 pm the evening of dec. 18, 2012. The aircraft was scheduled to land at pan at approximately 5:30 pm to pick up packages from the local ups currier. The ups driver and his boss were waiting on the ramp at Payson to deliver additional packages to the cargo flight. Neither of these personnel observed or heard an aircraft in the area during the time they were present at the airport. After waiting 20 minutes for the ameriflight aircraft to arrive the ground personnel decided to take the packages for delivery to phx by ground vehicle.
Air traffic control tapes recovered after the crash were reviewed and the following is a summary of the information which they contained:
At approximately 6:11 pm (1:11 zulu time) the pilot contacted albuquerque center (zab) and requested an IFR clearance from his present position to phoenix.
The pilot identified the aircraft as ameriflight 3863 but zab mis-heard the flight number and identified the aircraft as (ameriflight) amf 3853 in subsequent radio communications. The pilot responded to these calls and did not correct the number read out.
Zab gave the aircraft a squawk code (2651) and the pilot stated that he was at 13,500 ft. and wanted to get an IFR clearance to phx. At 6:14 (1:14 zulu) zab cleared him direct to phx with a restriction to cross 40 miles north of phx at 10,000 ft. phx altimeter reading was 29.74.
The aircraft proceeded to descend to 10,000 ft and stabled out at that altitude at 6:19 (1:19 zulu).
At 6:23:56 pm (1:23:56 zulu) the pilot asked for lower altitude because he was ?getting some heavy up and down drafts? (Turbulence). Zab told him they were unable to get him lower because the minimum vectoring altitude (mva) in the area was 9,700 ft and his mode c was indicating the aircraft was at 9,500 ft. at 1:24:17 the pilot acknowledged the transmission with a ?roger? And the tape indicates the aircraft climbed back up to 10,000 ft.
From 1:24:24 to 1:24:27 zulu the ATC controller made a call to another aircraft and blocked a transmission which was not picked up on the ATC tape. The broken unreadable transmission lasted until 1:24:33. At 1:24:35 thru 1:24:39 zab transmitted asking who was calling & stated ?you were broken and un-readable, say again please?. Zab then gave another aircraft instructions. At 1:25:18 zab called ameriflight 3863 and stated ?radar contact lost?. Within the time of 1:24:24 and 1:24:33 the amf 3853 ATC tag changed from indicating altitude and airspeed to a ?primary? Target.
For the next minute zab controller called ameriflight 3853 several times but got no response back from the pilot. Zab then called a medivac king air (call sign lifeguard 918) which was flying along the same flight path behind the ameriflight aircraft 10 miles, and was at 12, 000 ft. zab requested lifeguard 918 pilot to try to contact amf 3853. This lifeguard pilot made several attempts to contact the aircraft but no transmission was received from ameriflight aircraft. Zab asked lifeguard to check whether an ELT beacon could be heard. The response was negative. Within 4 minutes zab again asked the pilot of lifeguard 918 to see if he could see any lights or fire in the area he was flying over. The pilot stated that he was in and out of the tops of the clouds and could see nothing below. He also stated that he was experiencing moderate turbulence where he was at.
At 2:04 zulu ATC issued an alnot on the aircraft and a search & rescue effort was started to look for the aircraft in the area last known from ATC radar plots.
Both AZ highway patrol and civil air patrol conducted sar missions that evening and the next day. Because of darkness and bad weather conditions the evening of dec. 18 the aircraft crash site was not located until the next morning at appr
As the FAA filed it
PILOT WAS CONDUCTING CARGO FLIGHT FROM HOLBROOK AZ (P14) TO PHOENIX, AZ (PHX) WITH A SCHEDULED STOP IN PAYSON AZ (PAN) TO PICK UP & DELIVER EXPRESS PACKAGES FOR UPS. AIRCRAFT WAS SEEN DEPARTING HOLBROOK AIRPORT BETWEEN 4:50 ? 5:00 PM THE EVENING OF DEC. 18, 2012. THE AIRCRAFT WAS SCHEDULED TO LAND AT PAN AT APPROXIMATELY 5:30 PM TO PICK UP PACKAGES FROM THE LOCAL UPS CURRIER. THE UPS DRIVER AND HIS BOSS WERE WAITING ON THE RAMP AT PAYSON TO DELIVER ADDITIONAL PACKAGES TO THE CARGO FLIGHT. NEITHER OF THESE PERSONNEL OBSERVED OR HEARD AN AIRCRAFT IN THE AREA DURING THE TIME THEY WERE PRESENT AT THE AIRPORT. AFTER WAITING 20 MINUTES FOR THE AMERIFLIGHT AIRCRAFT TO ARRIVE THE GROUND PERSONNEL DECIDED TO TAKE THE PACKAGES FOR DELIVERY TO PHX BY GROUND VEHICLE.
AIR TRAFFIC CONTROL TAPES RECOVERED AFTER THE CRASH WERE REVIEWED AND THE FOLLOWING IS A SUMMARY OF THE INFORMATION WHICH THEY CONTAINED:
AT APPROXIMATELY 6:11 PM (1:11 ZULU TIME) THE PILOT CONTACTED ALBUQUERQUE CENTER (ZAB) AND REQUESTED AN IFR CLEARANCE FROM HIS PRESENT POSITION TO PHOENIX.
THE PILOT IDENTIFIED THE AIRCRAFT AS AMERIFLIGHT 3863 BUT ZAB MIS-HEARD THE FLIGHT NUMBER AND IDENTIFIED THE AIRCRAFT AS (AMERIFLIGHT) AMF 3853 IN SUBSEQUENT RADIO COMMUNICATIONS. THE PILOT RESPONDED TO THESE CALLS AND DID NOT CORRECT THE NUMBER READ OUT.
ZAB GAVE THE AIRCRAFT A SQUAWK CODE (2651) AND THE PILOT STATED THAT HE WAS AT 13,500 FT. AND WANTED TO GET AN IFR CLEARANCE TO PHX. AT 6:14 (1:14 ZULU) ZAB CLEARED HIM DIRECT TO PHX WITH A RESTRICTION TO CROSS 40 MILES NORTH OF PHX AT 10,000 FT. PHX ALTIMETER READING WAS 29.74.
THE AIRCRAFT PROCEEDED TO DESCEND TO 10,000 FT AND STABLED OUT AT THAT ALTITUDE AT 6:19 (1:19 ZULU).
AT 6:23:56 PM (1:23:56 ZULU) THE PILOT ASKED FOR LOWER ALTITUDE BECAUSE HE WAS ?GETTING SOME HEAVY UP AND DOWN DRAFTS? (TURBULENCE). ZAB TOLD HIM THEY WERE UNABLE TO GET HIM LOWER BECAUSE THE MINIMUM VECTORING ALTITUDE (MVA) IN THE AREA WAS 9,700 FT AND HIS MODE C WAS INDICATING THE AIRCRAFT WAS AT 9,500 FT. AT 1:24:17 THE PILOT ACKNOWLEDGED THE TRANSMISSION WITH A ?ROGER? AND THE TAPE INDICATES THE AIRCRAFT CLIMBED BACK UP TO 10,000 FT.
FROM 1:24:24 TO 1:24:27 ZULU THE ATC CONTROLLER MADE A CALL TO ANOTHER AIRCRAFT AND BLOCKED A TRANSMISSION WHICH WAS NOT PICKED UP ON THE ATC TAPE. THE BROKEN UNREADABLE TRANSMISSION LASTED UNTIL 1:24:33. AT 1:24:35 THRU 1:24:39 ZAB TRANSMITTED ASKING WHO WAS CALLING & STATED ?YOU WERE BROKEN AND UN-READABLE, SAY AGAIN PLEASE?. ZAB THEN GAVE ANOTHER AIRCRAFT INSTRUCTIONS. AT 1:25:18 ZAB CALLED AMERIFLIGHT 3863 AND STATED ?RADAR CONTACT LOST?. WITHIN THE TIME OF 1:24:24 AND 1:24:33 THE AMF 3853 ATC TAG CHANGED FROM INDICATING ALTITUDE AND AIRSPEED TO A ?PRIMARY? TARGET.
FOR THE NEXT MINUTE ZAB CONTROLLER CALLED AMERIFLIGHT 3853 SEVERAL TIMES BUT GOT NO RESPONSE BACK FROM THE PILOT. ZAB THEN CALLED A MEDIVAC KING AIR (CALL SIGN LIFEGUARD 918) WHICH WAS FLYING ALONG THE SAME FLIGHT PATH BEHIND THE AMERIFLIGHT AIRCRAFT 10 MILES, AND WAS AT 12, 000 FT. ZAB REQUESTED LIFEGUARD 918 PILOT TO TRY TO CONTACT AMF 3853. THIS LIFEGUARD PILOT MADE SEVERAL ATTEMPTS TO CONTACT THE AIRCRAFT BUT NO TRANSMISSION WAS RECEIVED FROM AMERIFLIGHT AIRCRAFT. ZAB ASKED LIFEGUARD TO CHECK WHETHER AN ELT BEACON COULD BE HEARD. THE RESPONSE WAS NEGATIVE. WITHIN 4 MINUTES ZAB AGAIN ASKED THE PILOT OF LIFEGUARD 918 TO SEE IF HE COULD SEE ANY LIGHTS OR FIRE IN THE AREA HE WAS FLYING OVER. THE PILOT STATED THAT HE WAS IN AND OUT OF THE TOPS OF THE CLOUDS AND COULD SEE NOTHING BELOW. HE ALSO STATED THAT HE WAS EXPERIENCING MODERATE TURBULENCE WHERE HE WAS AT.
AT 2:04 ZULU ATC ISSUED AN ALNOT ON THE AIRCRAFT AND A SEARCH & RESCUE EFFORT WAS STARTED TO LOOK FOR THE AIRCRAFT IN THE AREA LAST KNOWN FROM ATC RADAR PLOTS.
BOTH AZ HIGHWAY PATROL AND CIVIL AIR PATROL CONDUCTED SAR MISSIONS THAT EVENING AND THE NEXT DAY. BECAUSE OF DARKNESS AND BAD WEATHER CONDITIONS THE EVENING OF DEC. 18 THE AIRCRAFT CRASH SITE WAS NOT LOCATED UNTIL THE NEXT MORNING AT APPR
NTSB investigation
The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.
Other reports on N62959 · 2
Matched to the same aircraft by N-number and date.