What happened
The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.
On July 27th, 2022 at 12:52 PST, the pilot reported an issue with the autopilot causing a cabin host to fall and sustain serious injury.
privacy data omitted Had just flown saratoga airport (5B2) to sfo. The pilot in command flew the saratoga to sfo leg. The PIC allowed the second in command (SIC) to take over the next leg of the flight. This was to be a reposition flight, so there were no passengers, and one hostess on board the aircraft.
After the aircraft took off it was under normal climb rate with no problems. Auto pilot was engaged around 2,000 feet that’s when the aircraft received its first cas message. Cas message was acknowledged, and around 23 to 24,000 ft, a second cas message was received. PIC decided it was a legit problem and began reviewing the checklist. Cas message was ap holding nose down.
During this time PIC resumed control of the aircraft and gave monitoring duties to SIC. SIC began reviewing the checklist on the ipad.
The PIC stated he held the yoke while looking at the rate of climb, and parameters appeared normal for the conditions. The PIC stated he began to slow the rate of climb. During this time the auto pilot disconnected, and the aircraft lost multi-function display #2 (MFD #2). When the autopilot disconnected there was a quick nose up, and a couple of oscillations before a straight and level flight.
The PIC announced a stop climb, then stabilized the aircraft.
Shortly after the incident the hostess declared being hurt.
PIC decided to return to sfo, and ATC gave them direct clearance to sfo.
During the return flight to sfo, MFD #2 was still not working.
Flight was not declared an emergency on the return to sfo, and aircraft was back under control. During the return flight the PIC stated the controls felt “heavy.”
Aircraft landed normally on runway 28R and returned to FBO and the PIC performed a shutdown checklist.
At the FBO the hostess was removed by emergency first responders.
Friday July 28th, 2022 FAA was onsite at sfo with Bombardier maintenance crew. After gaining access to the aircraft preliminary inspections was started by Bombardier crew with FAA oversight.
During the initial inspection the following items were performed:
• Disable cockpit voice recorder (CVR)
• On-wing download of the flight data recorder (FDR)
• Removal of the FDR
• Download the horizontal stabilizer trim control unit non-volatile memory (hstcu nvm)
• Download the mdc
On July 29th data was analyzed and it the FDR and CVR were sent to NTSB for continued analyzation.
On August 29th Bombardier crew and the FAA returned to the aircraft with for more testing and removal of components.
On September 28th, flight guidance computers (fgc), horizontal stabilizer trim control, and the hstecu were removed and sent to the NTSB for further analyzation.
At this point this is an ongoing NTSB investigation. If there is more information relevant to the accident that is received the FAA, this accident report will be updated.
As the FAA filed it
ON JULY 27TH, 2022 AT 12:52 PST, THE PILOT REPORTED AN ISSUE WITH THE AUTOPILOT CAUSING A CABIN HOST TO FALL AND SUSTAIN SERIOUS INJURY.
^PRIVACY DATA OMITTED^ HAD JUST FLOWN SARATOGA AIRPORT (5B2) TO SFO. THE PILOT IN COMMAND FLEW THE SARATOGA TO SFO LEG. THE PIC ALLOWED THE SECOND IN COMMAND (SIC) TO TAKE OVER THE NEXT LEG OF THE FLIGHT. THIS WAS TO BE A REPOSITION FLIGHT, SO THERE WERE NO PASSENGERS, AND ONE HOSTESS ON BOARD THE AIRCRAFT.
AFTER THE AIRCRAFT TOOK OFF IT WAS UNDER NORMAL CLIMB RATE WITH NO PROBLEMS. AUTO PILOT WAS ENGAGED AROUND 2,000 FEET THAT’S WHEN THE AIRCRAFT RECEIVED ITS FIRST CAS MESSAGE. CAS MESSAGE WAS ACKNOWLEDGED, AND AROUND 23 TO 24,000 FT, A SECOND CAS MESSAGE WAS RECEIVED. PIC DECIDED IT WAS A LEGIT PROBLEM AND BEGAN REVIEWING THE CHECKLIST. CAS MESSAGE WAS AP HOLDING NOSE DOWN.
DURING THIS TIME PIC RESUMED CONTROL OF THE AIRCRAFT AND GAVE MONITORING DUTIES TO SIC. SIC BEGAN REVIEWING THE CHECKLIST ON THE IPAD.
THE PIC STATED HE HELD THE YOKE WHILE LOOKING AT THE RATE OF CLIMB, AND PARAMETERS APPEARED NORMAL FOR THE CONDITIONS. THE PIC STATED HE BEGAN TO SLOW THE RATE OF CLIMB. DURING THIS TIME THE AUTO PILOT DISCONNECTED, AND THE AIRCRAFT LOST MULTI-FUNCTION DISPLAY #2 (MFD #2). WHEN THE AUTOPILOT DISCONNECTED THERE WAS A QUICK NOSE UP, AND A COUPLE OF OSCILLATIONS BEFORE A STRAIGHT AND LEVEL FLIGHT.
THE PIC ANNOUNCED A STOP CLIMB, THEN STABILIZED THE AIRCRAFT.
SHORTLY AFTER THE INCIDENT THE HOSTESS DECLARED BEING HURT.
PIC DECIDED TO RETURN TO SFO, AND ATC GAVE THEM DIRECT CLEARANCE TO SFO.
DURING THE RETURN FLIGHT TO SFO, MFD #2 WAS STILL NOT WORKING.
FLIGHT WAS NOT DECLARED AN EMERGENCY ON THE RETURN TO SFO, AND AIRCRAFT WAS BACK UNDER CONTROL. DURING THE RETURN FLIGHT THE PIC STATED THE CONTROLS FELT “HEAVY.”
AIRCRAFT LANDED NORMALLY ON RUNWAY 28R AND RETURNED TO FBO AND THE PIC PERFORMED A SHUTDOWN CHECKLIST.
AT THE FBO THE HOSTESS WAS REMOVED BY EMERGENCY FIRST RESPONDERS.
FRIDAY JULY 28TH, 2022 FAA WAS ONSITE AT SFO WITH BOMBARDIER MAINTENANCE CREW. AFTER GAINING ACCESS TO THE AIRCRAFT PRELIMINARY INSPECTIONS WAS STARTED BY BOMBARDIER CREW WITH FAA OVERSIGHT.
DURING THE INITIAL INSPECTION THE FOLLOWING ITEMS WERE PERFORMED:
• DISABLE COCKPIT VOICE RECORDER (CVR)
• ON-WING DOWNLOAD OF THE FLIGHT DATA RECORDER (FDR)
• REMOVAL OF THE FDR
• DOWNLOAD THE HORIZONTAL STABILIZER TRIM CONTROL UNIT NON-VOLATILE MEMORY (HSTCU NVM)
• DOWNLOAD THE MDC
ON JULY 29TH DATA WAS ANALYZED AND IT THE FDR AND CVR WERE SENT TO NTSB FOR CONTINUED ANALYZATION.
ON AUGUST 29TH BOMBARDIER CREW AND THE FAA RETURNED TO THE AIRCRAFT WITH FOR MORE TESTING AND REMOVAL OF COMPONENTS.
ON SEPTEMBER 28TH, FLIGHT GUIDANCE COMPUTERS (FGC), HORIZONTAL STABILIZER TRIM CONTROL, AND THE HSTECU WERE REMOVED AND SENT TO THE NTSB FOR FURTHER ANALYZATION.
AT THIS POINT THIS IS AN ONGOING NTSB INVESTIGATION. IF THERE IS MORE INFORMATION RELEVANT TO THE ACCIDENT THAT IS RECEIVED THE FAA, THIS ACCIDENT REPORT WILL BE UPDATED.
NTSB investigation
The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.