Flight Details
Aircraft Type: Airbus A321-271NX (A321neo) Operator: Frontier Airlines Registration: N607FR Flight Number: F93506 Route: Orlando International Airport (MCO), Florida to Luis Muñoz Marín International Airport (SJU), San Juan, Puerto Rico Date of Incident: 15 April 2025 (local), 16 April 2025 (UTC) Total Occupants: 228 (passengers and crew) Weather Conditions: Visual meteorological conditions; calm winds, visibility 10SM, scattered cloud at 2,500–3,000 ft; ambient temperature 25–26°C
Introduction
On the evening of 15 April 2025, a Frontier Airlines Airbus A321neo suffered a hard touchdown on runway 10 at San Juan’s Luis Muñoz Marín International Airport, resulting in a go-around and subsequent engine flame emissions during climb-out. The aircraft was performing flight F93506 inbound from Orlando with 228 people on board. Following the severe landing impact, debris was suspected on the runway and the aircraft initiated a low approach inspection before safely landing on runway 08 approximately 40 minutes later. The left engine exhibited sustained flame emissions during the go-around, prompting passenger concern and airport runway closures. No injuries were reported, and the incident remains under investigation.
Sequence of Events
The A321neo was on final approach to runway 10 at San Juan at approximately 21:40 local time. Conditions were favourable, with light surface winds from the east and clear visibility. According to eyewitness reports and post-landing passenger accounts, the aircraft touched down with a pronounced impact, described by the operator and the FAA as a “hard landing.”
Immediately after touchdown, the aircraft initiated a go-around. During the initial climb, the left-hand engine (Pratt & Whitney PW1133G) emitted a continuous streak of visible flame for several seconds. No fire alarm was triggered on board, but passengers observed bright flashes and reported moments of panic as the aircraft climbed away from the runway.
Air Traffic Control issued NOTAMs closing both runways at the airport following the incident, initially advising of debris on the landing runway. The aircraft continued outbound from San Juan, entering a holding pattern over the ocean while the flight crew ran checklists related to landing gear and engine status.
Approximately 27 minutes later, the aircraft performed a low approach to runway 08 to allow visual inspection of the landing gear and possible structural damage. Following the low pass, the aircraft was cleared for a full-stop landing on runway 08, which was executed without further incident. The aircraft rolled out and vacated at the end of the runway before stopping on the parallel taxiway for inspection.
Runway 08 was reopened shortly after the aircraft cleared the runway. Runway 10 remained closed for an extended period while airport personnel inspected for surface debris and signs of damage.
Crew & Communication
The flight crew’s response to the hard landing was immediate and decisive, initiating a go-around without delay and communicating with ATC regarding abnormal engine behaviour and gear concerns. Coordination between the crew and tower ensured prioritisation of airspace and clear instructions for traffic in the vicinity.
During the go-around, the engine flame event was not reported as an in-flight fire, suggesting either a transient compressor surge, fuel-rich ignition streak, or temporary combustion instability—conditions not uncommon following a hard landing when engine parameters may briefly fluctuate under asymmetric loads or disrupted airflow.
The crew completed relevant checklists and held to assess the landing gear status before conducting a low approach. Their communication remained composed, and their actions demonstrated strict adherence to Airbus abnormal procedures.
Aircraft Systems & Technical Analysis
The Airbus A321-271NX involved in the incident was equipped with Pratt & Whitney PW1133G-JM geared turbofan engines. These engines are known for their fuel efficiency but have had operational sensitivity to rapid power changes, altitude restarts, and thermal management in certain flight conditions.
The engine’s flame emission during the climb-out is being treated as a transient anomaly rather than a fire. Flame streaking can result from a hot section temperature spike, fuel-air mixture imbalance, or a momentary surge event. No ECAM warning or fire detection activation was reported, nor was a fire suppression system deployed.
The aircraft’s landing gear sustained an unknown degree of load from the hard impact on runway 10. Following the go-around, the crew received indications suggesting the need to verify landing gear status. The decision to conduct a low approach was a precautionary measure to rule out gear misalignment, collapsed struts, or hydraulic leaks.
After safely landing on runway 08, the aircraft remained stationary on a taxiway, pending visual inspection by ground crews. The aircraft was confirmed to be intact but remained on the ground for at least 17 hours post-landing, indicating ongoing inspection or pending component replacement.
Passenger Experience & Cabin Conditions
Passengers reported a sharp, jarring touchdown followed by a rapid climb and visible engine flame out of the left window. Some described panic and anxiety during the climb-out, particularly as the aircraft re-entered holding without initial explanation.
Cabin crew would have briefed passengers during the holding phase, while the flight crew handled operational priorities. There were no injuries reported, and the aircraft cabin did not experience smoke, decompression, or electrical anomalies during the sequence.
Upon landing, the aircraft taxied to a holding point and passengers were likely deplaned using ground stairs or air bridge following inspection clearance. Frontier has not publicly stated whether compensation or rebooking assistance was provided.
Emergency Response & Aftermath
Both runways at San Juan were closed following the initial landing attempt, with NOTAMs issued citing foreign object debris and hard landing inspection. Airport fire and rescue units were deployed as a precaution, though no fire or structural failure occurred.
Runway 08 was cleared and reopened shortly after the successful second landing. Runway 10 remained closed for further surface inspection, and markings were evaluated for rubber deposits, scrape marks, or debris.
The FAA issued a formal statement identifying the event as a “hard runway contact damaging the landing gear,” confirming that the investigation is underway. Airport operations resumed later that night with some delays to incoming traffic.
Investigation Status
The Federal Aviation Administration is leading the investigation in cooperation with Airbus and Pratt & Whitney technical representatives. Flight data and cockpit voice recorders are expected to be downloaded to confirm impact forces, touchdown rate, pitch angle, and engine data during the go-around sequence.
Focus areas include:
Vertical speed and sink rate at touchdown Auto thrust and flight mode behaviour during final approach Engine performance parameters during power increase Gear load absorption and post-impact extension integrity Engine flame source and risk categorisation
The aircraft remains grounded at San Juan and may require gear servicing, shock absorber recalibration, or engine hot section inspection prior to re-entry into service.
Root Cause & Contributing Factors
Preliminary evidence points to a hard landing caused by excess vertical descent rate or possible misjudgement in the flare. If auto-pilot was disengaged too late, or the flare was mistimed due to tailwind, pitch attitude, or unstable approach cues, the touchdown impact may have exceeded gear design limits.
The engine flame emission is believed to be a secondary effect, possibly triggered by rapid throttle advancement and abnormal airflow following ground contact and rotation.
Contributing factors under review include:
Flight path stability on short final Wind shear or localised thermal activity near runway threshold Interaction between hard landing energy and engine response during go-around
Safety Recommendations & Industry Impact
While the investigation is ongoing, Frontier Airlines may revise guidance around approach profiles into short Caribbean runways with high humidity and thermal variance, especially in night operations.
Pratt & Whitney may issue an inspection advisory for engines that experience go-arounds following hard landings, especially if hot section performance may have been stressed.
No regulatory changes have been made, but the event adds to a growing industry emphasis on precise approach management and go-around execution under non-nominal conditions.
Conclusion
The Frontier Airlines A321neo incident at San Juan demonstrates how a hard landing—potentially caused by descent mismanagement or micro-meteorological factors—can cascade into secondary technical events, such as engine flameout effects and gear concerns. Despite visible anomalies, the aircraft was safely recovered and returned to the airport without injury or loss.
The investigation will determine the full sequence and whether human, environmental, or system factors combined to create a near-miss scenario requiring procedural refinement and operational learning.
Disclaimer
This article is based on publicly available information and reports at the time of writing. While every effort has been made to ensure accuracy, we cannot guarantee the completeness of the information provided.
If you are the rightful owner of any referenced content or images and wish them to be removed, please contact takedown@cockpitking.com.
