OpenAirDocs.org

20260731011389I

Incident · Minor damage
Open the Markdown

FAA incident report · Airbus A320-214 · San Francisco, CA · July 31, 2026

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
July 31, 2026 · 15:55 local
Place
San Francisco, CA
Airport
San Francisco International
Phase of flight
Cruise/Level Flight
Operating rules
Foreign air carrier (Part 129)
Operator
ARNF
Damage
Minor damage
Aircraft
C-GJVT
Reported as
Airbus A320-214
Reported engine
CFM International CFM56-5B4/P
People aboard
152
Fatal injuries
0
Other injuries
0

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

During cruise approx. 90 minutes into the flight crew experienced an engine 1 stall that quickly recovered on its own to stable engine parameters. Flight crew was in contact with dispatch and maintenance control, decision to continue to destination was made.

Approx. 10 minutes prior to top of descent, ATC requested descend from FL340 to FL320 and slow to 250KIAS. Following instructions, vibrations through the airframe were felt and "eng 1 high vibration" ecam message. Flight crew began the engine high vibration procedures, an eng 1 stall ecam followed by an eng 1 fail ecam appeared. Flight crew began the engine fail at high altitude cruise procedure and made a mayday call to ATC as well as requesting a lower altitude as the aircraft was unable to maintain altitude.

Engine 1 automatically relit and immediately the high vibrations returned, along with the same sequence of ecam messages. The flight crew made the decision to start the engine shutdown procedure. Flight crew followed all established procedures.

In-flight crew and passengers were briefed of the situation.

Aside from being a single engine approach, the approach and landing were otherwise uneventful. The aircraft was stopped on the runway for an inspection by ARFF, then continued to gate D11 under its own power.

Maintenance replaced engine 1 and aircraft returned to service August 6, 2026.

As the FAA filed it

DURING CRUISE APPROX. 90 MINUTES INTO THE FLIGHT CREW EXPERIENCED AN ENGINE 1 STALL THAT QUICKLY RECOVERED ON ITS OWN TO STABLE ENGINE PARAMETERS. FLIGHT CREW WAS IN CONTACT WITH DISPATCH AND MAINTENANCE CONTROL, DECISION TO CONTINUE TO DESTINATION WAS MADE.

APPROX. 10 MINUTES PRIOR TO TOP OF DESCENT, ATC REQUESTED DESCEND FROM FL340 TO FL320 AND SLOW TO 250KIAS. FOLLOWING INSTRUCTIONS, VIBRATIONS THROUGH THE AIRFRAME WERE FELT AND "ENG 1 HIGH VIBRATION" ECAM MESSAGE. FLIGHT CREW BEGAN THE ENGINE HIGH VIBRATION PROCEDURES, AN ENG 1 STALL ECAM FOLLOWED BY AN ENG 1 FAIL ECAM APPEARED. FLIGHT CREW BEGAN THE ENGINE FAIL AT HIGH ALTITUDE CRUISE PROCEDURE AND MADE A MAYDAY CALL TO ATC AS WELL AS REQUESTING A LOWER ALTITUDE AS THE AIRCRAFT WAS UNABLE TO MAINTAIN ALTITUDE.

ENGINE 1 AUTOMATICALLY RELIT AND IMMEDIATELY THE HIGH VIBRATIONS RETURNED, ALONG WITH THE SAME SEQUENCE OF ECAM MESSAGES. THE FLIGHT CREW MADE THE DECISION TO START THE ENGINE SHUTDOWN PROCEDURE. FLIGHT CREW FOLLOWED ALL ESTABLISHED PROCEDURES.

IN-FLIGHT CREW AND PASSENGERS WERE BRIEFED OF THE SITUATION.

ASIDE FROM BEING A SINGLE ENGINE APPROACH, THE APPROACH AND LANDING WERE OTHERWISE UNEVENTFUL. THE AIRCRAFT WAS STOPPED ON THE RUNWAY FOR AN INSPECTION BY ARFF, THEN CONTINUED TO GATE D11 UNDER ITS OWN POWER.

MAINTENANCE REPLACED ENGINE 1 AND AIRCRAFT RETURNED TO SERVICE AUGUST 6, 2026.