United 737-900 Diverts to Jacksonville After Crew Reports Engine Issue Minutes Into Climb

A short flight that ended in Jacksonville
United Airlines Flight 2746, a Boeing 737-900ER scheduled to fly from Orlando International Airport to Washington Dulles International Airport, diverted to Jacksonville International Airport on the morning of September 25, 2026, after the flight crew reported an issue with one of the aircraft's two engines. The aircraft, registered N66831, landed without further incident, and all passengers and crew deplaned normally at the gate.
According to flight-tracking data reviewed by aviation incident trackers Aeroinside and AeroCorner, the aircraft pushed back from gate 40 at Orlando International at approximately 8:51 a.m. EDT. About 30 minutes into the climb, the crew selected transponder code 7700 — the universal signal for a general emergency that triggers heightened attention from air traffic control — and leveled the aircraft off at 22,000 feet rather than continuing to climb toward cruising altitude. The crew then requested a diversion to Jacksonville, the nearest suitable airport along the route.
The jet touched down on runway 08 at Jacksonville International at 10:03 a.m. EDT and reached the gate at 10:10 a.m., putting the total elapsed time between pushback and arrival at the diversion airport at a little over an hour. United confirmed the aircraft landed safely in Jacksonville "to address an issue with one engine," a description that indicates a mechanical concern rather than a structural or fire-related event, though the airline did not provide further technical detail in its public statement.
Fox News, which aired footage of the incident on its travel desk on September 29, reported that passengers described the aircraft shaking during the climb before the crew announced the diversion. That passenger account is consistent with, but not identical to, the sequence of transponder and altitude data reported by the flight-tracking sites; it has not been independently verified by air safety investigators, and this article treats it as an unconfirmed passenger impression rather than an established fact about the mechanical cause.
What is confirmed, and what is not
It is important to separate what has been verified from what remains under investigation. The following details are consistently reported across multiple sources:
- The flight involved was United 2746, a Boeing 737-900ER, tail number N66831.
- The aircraft departed Orlando International Airport on September 25, 2026, bound for Washington Dulles.
- The crew squawked 7700 approximately 30 minutes after departure and requested a diversion.
- The aircraft landed safely at Jacksonville International Airport.
- United described the cause as "an issue with one engine."
- No injuries were reported among the 179 passengers and six crew members aboard.
- Passengers deplaned normally at the gate rather than via emergency slides, indicating the crew and airport ground staff assessed the situation as not requiring an emergency evacuation.
What has not been established is the specific mechanical fault involved — whether it was, for example, a sensor warning, an oil-related indication, a bird strike, or another cause. United has not released a technical explanation beyond confirming an engine issue, and neither the NTSB nor the FAA had published a public docket or statement on the incident as of this writing. Under the framework used internationally for classifying aviation events — modeled on ICAO Annex 13 — an event where an aircraft lands safely with no injuries after a precautionary diversion is typically classified as a serious incident rather than an accident.
United said a replacement Boeing 737-900 was arranged to complete the journey to Washington Dulles, and that aircraft arrived with a delay of approximately four hours relative to the original schedule. The diverted aircraft remained in Jacksonville following the landing; its return to service, and whatever maintenance inspection preceded that return, has not been publicly detailed by the airline.

Why engine-related diversions get this much scrutiny
Modern twin-engine airliners, including the 737-900ER, are certified to fly and land safely on a single engine, and flight crews train extensively for exactly this kind of scenario. A diversion prompted by an engine indication is not, by itself, evidence of a severe or unusual failure; it reflects the conservative, safety-first culture that governs how airline crews respond to any anomaly in flight. Squawking 7700 is a standard and expected step that ensures a diverting aircraft receives priority handling from air traffic control, clearing airspace and runway access ahead of aircraft that are not experiencing a problem. It is not, on its own, an indication of how serious the underlying issue turned out to be.
That said, engine events attract close attention from regulators and manufacturers because the data from each occurrence feeds into fleet-wide reliability tracking. The 737-900ER is a well-established member of the Next Generation 737 family, powered by CFM56-7B engines in United's configuration, with an extensive service history. Isolated engine-related diversions occur across the global fleet regularly and, in the overwhelming majority of cases, are resolved through routine maintenance without any airworthiness directive or broader fleet action. Whether this event leads to any regulatory follow-up will depend on findings not yet made public.
The airport's role
Jacksonville International Airport, designated JAX, is not on United's list of Orlando-to-Dulles routing but functions as a viable diversion field for traffic along the Southeast US corridor, with a runway length and emergency response capability suited to handling widebody and narrowbody diversions. Ground crews and airport operations staff at JAX coordinated the aircraft's arrival at gate A1, and passengers were deplaned through the terminal in the ordinary manner rather than via emergency evacuation procedures, which is itself informative: airlines and airports reserve slide evacuations for situations assessed in real time as posing an immediate hazard, such as fire or smoke in the cabin. The absence of an emergency evacuation in this case is consistent with a controlled, precautionary diversion rather than an in-flight emergency of the most serious category.
What happens next
In the ordinary course of events following a diversion of this kind, the airline's own maintenance technicians would inspect the affected engine before the aircraft returns to revenue service, and, depending on what that inspection finds, the airline may or may not be required to notify the FAA under existing reporting rules. If the inspection reveals a fault pattern that could affect other aircraft — for instance, a part showing wear inconsistent with its expected service life — that could, in principle, prompt a service bulletin from Boeing or an airworthiness directive affecting other 737-900ER operators. At this stage, there is no public indication this incident has triggered, or is expected to trigger, any such action. Readers should treat claims about the specific cause as unconfirmed until an official finding is released.
United Airlines has not indicated whether it considers the incident closed from an internal review standpoint, and neither the FAA nor NTSB had, as of publication, listed this event in any public incident database with additional technical findings beyond what United itself disclosed.
How this fits into a busier season for diversions
September 2026 has, by the count kept by flight-tracking and incident-monitoring sites, seen a steady drum of squawk-7700 diversions across multiple US and international carriers, spanning medical emergencies, pressurization concerns, and mechanical indications of varying severity. Aviation safety analysts caution against reading a rising count of publicly reported diversions as evidence of declining fleet reliability on its own, since visibility into these events has increased substantially in recent years. Real-time flight-tracking tools and an expanding roster of aviation-focused outlets that monitor transponder codes as they happen mean incidents that might once have gone unreported are now documented within minutes. That greater visibility is generally regarded as a net positive for transparency, even though it can create an impression of increased frequency not necessarily borne out by accident and incident rate statistics, which regulators calculate per flight-hour rather than as a raw event count.
For United specifically, a single engine-related diversion on one aircraft in a fleet of several hundred 737-family jets is not, by itself, indicative of a broader fleet issue. Airlines and regulators distinguish between isolated maintenance events, which occur routinely across every operator's fleet, and pattern failures, where multiple similar events point to a common root cause. Nothing in the public reporting indicates investigators have identified a pattern connecting this event to any other recent 737-900ER incident, and readers should treat any such connection as speculative unless the FAA, NTSB, or Boeing states otherwise.
The passenger experience of a diversion
For the 179 passengers aboard, the practical experience of the diversion likely followed a familiar script: a measured, non-alarming crew announcement, a period of uncertainty while the aircraft held at a lower altitude en route to the alternate airport, and then a landing followed by a wait at an unfamiliar airport for rebooking information. United's provision of a replacement aircraft to complete the Jacksonville-to-Dulles leg, arriving roughly four hours behind schedule, is a fairly standard airline response, allowing passengers to reach their destination the same day. Passengers seeking compensation for a diversion of this kind should note that US airline obligations for mechanical delays differ from the European Union's stronger passenger-compensation rules, and United's own contract of carriage governs what, if anything, affected passengers are owed.