# Accident 20220221001299A: Raytheon Aircraft Company HAWKER 800XP, Aspen, CO, February 21, 2022 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: February 21, 2022, 11:30 local time - Place: Aspen, CO - Airport: Aspen-Pitkin County/Sardy Fld - Damage: Substantial damage - Phase of flight: Takeoff: Rotation - Operating rules: Air taxi and commuter (Part 135) - Operator: N52A - Location: 39.2326° N, 106.8735° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=39.2326&lon=-106.8735&mi=10 - Aircraft: N99AP, a cancelled registration (https://openairdocs.org/deregistered/N99AP-2024-05-01) (OpenAirDocs) - Registry model: Raytheon HAWKER 800XP (registry code 7150012, https://openairdocs.org/model/raytheon-hawker-800xp) (OpenAirDocs) - Registry engine: Alliedsign TFE731-5BR (registry code 02508, https://openairdocs.org/engine/alliedsign-tfe731-5br) (OpenAirDocs) - Reported make and model: RAYTHEON AIRCRAFT COMPANY HAWKER 800XP - Reported engine: ALLIEDSIGN TFE731-5BR - People aboard: 6 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Airline transport, flight instructor - Pilot flight hours: 7,054 total, 5,273 in this make and model - NTSB investigation: [NTSB CEN22LA130](https://openairdocs.org/ntsb/CEN22LA130) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20220221001299A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. PILOTS STATED THAT THEY REVIEWED THE WEATHER FOR THE PLANNED FLIGHT TO AUSTIN, TEXAS. PART OF THAT DISCUSSION INVOLVED THE CURRENT ATIS WHICH WAS 170° AT 18 KNOTS GUSTING TO 30 KNOTS. BOTH PILOTS STATED THAT THE WINDS WERE BEYOND THE TAILWIND LIMIT OF 10 KNOTS FOR THE AIRCRAFT. THE SIC STATED THAT HE INPUT THE TAKEOFF NUMBERS INTO APG FOR A ZERO FLAP TAKEOFF AND FOR WINDS HE USED THE CONTINUOUS WIND SPEED THAT WAS SUPPLIED BY THE TOWER AS 180° AT 10 KNOTS. PILOTS STATED THAT PASSENGER LOADING AND PREFLIGHT CHECKS WHERE COMPLETED WITHOUT ISSUE. DURING TAXI OUT, THE PIC STATED THAT HE REQUESTED THE SIC CHECK THE TAKEOFF DISTANCE IF THEY USED FLAPS 15 INSTEAD OF NO FLAPS. THE SIC STATED SELECTING FLAPS 15 INSTEAD OF ZERO PROVIDED AN 800 FOOT TAKEOFF DISTANCE DECREASE. THE PIC STATED THAT HE REQUESTED THE CHANGE TO FLAPS 15 AND THE SIC SELECTED FLAPS 15 AND CHANGED THE V SPEEDS FOR TAKEOFF. PILOTS STATED THAT FLAPS 15 WAS SELECTED AND VERIFIED. AT THE END OF RUNWAY, THE CREW WAS DELAYED APPROXIMATELY 20 MINUTES FOR INBOUND TRAFFIC. ONCE CLEARED FOR TAKEOFF THE TOWER GAVE THE FOLLOWING REPORT FOR WINDS: 160° 16 GUSTING TO 25 INSTANTANEOUS 180° AT 10. PILOTS STATED THAT THE AIRCRAFT WAS TAXIED ONTO THE RUNWAY FOR A STATIC TAKEOFF. THE PIC RAN THE ENGINES UP AND STARTED THE TAKEOFF ROLL. PILOTS STATED CALL OUTS WERE MADE AND CROSSCHECKED. THE SIC CALLED OUT ROTATE AND THE PIC STATED THAT HE PULLED BACK ON THE YOKE AND THERE WAS NO INDICATION OF THE NOSE WHEEL COMING OFF THE GROUND OR THE AIRPLANE BECOMING AIRBORNE. FURTHER, THE PIC STATED THAT THE YOKE DID NOT HAVE ANY AIR RESISTANCE OR ANY PRESSURE ON IT AS HE EXPERIENCED NORMALLY IN HAWKERS. HE STATED THAT THE ELEVATOR AUTHORITY FELT THE SAME AS THOUGH THE AIRPLANE WAS STATIONARY ON THE GROUND. THE PIC CONTINUED PULLING THE YOKE FOR A FEW SECONDS AND WHEN HE WAS SURE THAT THE AIRPLANE WASN?T RESPONDING, HE CALLED FOR THE ABORT. PERFORMED THE ABORT PER THE FLIGHT MANUAL BUT DUE TO BEING BEYOND V1 THERE WAS NOT SUFFICIENT RUNWAY TO STOP THE AIRCRAFT. THE AIRCRAFT DEPARTED THE RUNWAY INTO DEEP SNOW. AFTER THE AIRPLANE STOPPED, THE PIC STATED THAT HE CLOSED BOTH LP COCKS TO SHUT DOWN THE ENGINES AND THE APU WHICH ALL WERE STILL RUNNING. HE TURNED OFF ALL ELECTRICAL POWER IN THE AIRPLANE. BOTH PILOTS STATED THAT THEY ENSURED ALL PASSENGERS WERE OK AND THEN EVACUATED THE AIRCRAFT. THE NTSB ALLOWED THE AIRCRAFT TO BE RECOVERED FROM THE END OF THE RUNWAY AND PLACED IN A SECURE AREA. ON FEBRUARY 23, 2022, THE IIC VISITED THE AIRCRAFT WRECKAGE. AN INTERIOR INSPECTION SHOWED THAT ALL ELECTRICAL SWITCHES WERE OFF IN THE COCKPIT. FLAP HANDLE WAS IN THE 25 POSITION AND TRIM TAB WAS IN THE GREEN ARC. FLIGHT CONTROL CONTINUITY TO THE ELEVATORS WAS CONFIRMED BY MOVING THE YOKE FORWARD AND AFT WITH THE ELEVATOR SURFACES RESPONDING CORRECTLY. UNABLE TO DETERMINE AILERON, RUDDER OR ELEVATOR TRIM CONTROL CONTINUITY DUE TO DAMAGE TO THE AIRCRAFT. THE WINGS HAD SEPARATED AS ONE PIECE AND WAS RESTING NEXT TO THE FUSELAGE. THE LANDING GEAR WERE INTACT AND ALL FOUR MAIN TIRES WERE HOLDING AIR. THE FLAPS WERE IN THE 15 POSITION BASED ON MEASUREMENTS OF THEIR POSITION ON THE WING. BOTH ENGINES TURNED FREELY BY HAND AND SHOWED FOD DAMAGE TO THE BLADES. THE COCKPIT VOICE RECORDER WAS RECOVERED BY MECHANICS AT A LATER DATE AND SENT TO THE NTSB. ADSB DATA SHOWED THE AIRCRAFT ACCELERATED TO A PEAK GROUND SPEED OF 165 KNOTS WITH 3000 FOOT OF RUNWAY REMAINING. TAKEOFF DATA SHOWED V SPEEDS: V1 111 KNOTS AND VR SPEED OF 121 KNOTS. NO INJURIES TO PASSENGERS OR CREW. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB CEN22LA130](https://openairdocs.org/ntsb/CEN22LA130), Feb 21, 2022: Raytheon Hawker 800XP (N99AP), Aspen, CO, substantial damage. Probable cause: The flight crew’s decision to takeoff in tailwind conditions that were consistently above the airplane’s tailwind limitation, which resulted in a runway overrun following an aborted takeoff.… ## Other reports on N99AP (1) Matched to the same aircraft by N-number and date. - [Incident 20210430001999I](https://openairdocs.org/incident/20210430001999I), Apr 30, 2021: Raytheon Aircraft Company HAWKER 800XP (N99AP), Miami, FL, No damage. During climb from (kopf) to (kteb) aircraft N99AP noticed an overheat annunciator light in the rear cargobay. Aircraft crew declared an emergency and landed in… From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.