Doomscroll News

Preliminary Analysis: JetBlue Flight 1230 In-Flight Upset and Diversion

Written by

David Gross

in

Executive Summary

On October 30, 2025, JetBlue Flight 1230 (N605JB) diverted to Tampa (TPA) during its flight from Cancun (CUN) to Newark (EWR).1 The crew reported a “flight control issue,” which the pilot described to passengers as a “computer malfunction”.3 This technical failure caused a sudden, uncontrolled altitude drop of approximately 100 feet in seven seconds during the cruise phase.5

This initial upset, not the subsequent controlled emergency descent 7, caused 15 to 20 passenger injuries.5 The injuries were non-life-threatening. They occurred primarily because the seatbelt sign was off, which threw passengers from their seats.4

The aircraft was immediately removed from service for inspection.2 The Federal Aviation Administration (FAA) has opened an investigation.2 A significant secondary finding was a 45-minute delay in medical treatment on the ground at TPA.4 This delay was attributed to a procedural “bottleneck” as U.S. Customs and Border Protection (CBP) processed the unscheduled international arrival.4

Preliminary Analysis: JetBlue Flight 1230 In-Flight Upset and Diversion

On October 30, 2025, JetBlue Flight 1230 experienced a significant in-flight upset.1 The scheduled international flight was traveling from Cancun, Mexico, to Newark, New Jersey.1 It resulted in an emergency diversion to Tampa International Airport (TPA).1 The flight crew reported a “flight control issue,” which manifested as a sudden, sharp drop in altitude.2 This event occurred during the cruise phase of flight. It caused injuries to multiple unbelted passengers. This analysis synthesizes available data to provide a preliminary overview of the incident’s timeline, the technical factors involved, and the subsequent procedural challenges. The purpose of this preliminary report is to inform stakeholders of the known facts and guide further investigation.

Reports indicate 15 to 20 passengers sustained non-life-threatening injuries.5 Following the upset, the crew declared an emergency.13 They executed a safe, controlled emergency descent to TPA. This descent is distinct from the initial uncontrolled drop.5

The aircraft involved, an Airbus A320 (N605JB), was removed from service for inspection.2 The Federal Aviation Administration (FAA) is investigating the “flight control issue” under Docket No. 2025-1426.2 A significant secondary finding involves a reported 45-minute delay in medical transport at TPA.4 This delay was attributed to “bureaucratic gridlock” during U.S. Customs and Border Protection (CBP) processing.4

Incident Identifiers and Flight Profile

The basic identifiers for the incident flight on October 30, 2025, are as follows:

  • Flight: JetBlue Flight 1230 (ICAO: JBU1230; IATA: B61230).1
  • Route: Cancun International Airport (CUN), Mexico, to Newark Liberty International Airport (EWR), New Jersey.1
  • Diversion Airport: Tampa International Airport (TPA), Florida.1
  • Aircraft Type: Airbus A320-232.1
  • Aircraft Registration: N605JB.1
  • Filed Altitude: Flight data indicates a filed cruise altitude of 35,000 feet or 36,000 feet.17

The Upset Event: Timeline and Dynamics

The in-flight emergency occurred during the cruise phase, approximately one hour and 45 minutes after departing Cancun.17 The aircraft was over the Gulf of Mexico at the time.16

The 100-Foot Upset vs. The 14,500-Foot Controlled Descent

Analysis of public statements and flight tracking data reveals two distinct altitude deviation events that have been conflated in some reports.

  1. The Initial Upset (The Cause): The aircraft experienced the sudden, uncontrolled event at approximately 1:48 p.m. ET (17:48 UTC) while cruising at 35,000 feet.5 Flight tracking data indicates this was a sharp drop of approximately 100 feet in under seven seconds.5 This violent pitch-down, despite its minor altitude change, would have created a significant negative or low-G environment in the cabin. This was sufficient to lift unsecured passengers, crew, and objects into the air.4 This aligns with passenger accounts.4
  2. The Emergency Descent (The Response): Following the upset and the crew’s declaration of an emergency, the pilots initiated a controlled emergency descent to divert to TPA. This is the source of reports describing much larger altitude losses. Flight data shows a descent of 14,500 feet over a five-minute period, followed by another 12,200-foot drop.8 Other data confirms the aircraft descended from its cruise at 35,000 feet to 18,125 feet in approximately six minutes (approx. 18:59 UTC to 19:05 UTC) during its diversion.7

It is essential to distinguish between these events. The 100-foot drop was the uncontrolled incident. The subsequent 14,500-foot descent was the intentional, procedural response by the flight crew to manage the emergency and divert.

The aircraft landed safely at TPA at approximately 2:19 p.m. ET.5

Weather and Atmospheric Conditions

In any aviation incident, weather is routinely assessed as a potential contributing factor. However, in this event, weather has been preliminarily ruled out as a causal factor.

  • Crew Reports: A passenger on board stated the pilot specifically announced the event was due to a “computer malfunction” and was not weather or hurricane related.4
  • ATC Communications: Reports from air traffic control communications state the weather was “calm” at the time of the incident.14
  • Meteorological Data: One report noted a strong cold front had recently passed through Florida, but no official connection has been made to the incident.5 National Weather Service (NWS) marine forecasts for the Gulf of Mexico on October 30-31, 2025, indicated moderate northerly to northwesterly winds and diminishing seas.29 No active SIGMETs (Significant Meteorological Information) or PIREPs (Pilot Reports) for severe turbulence were found in the available data.32 Global jet stream forecast charts show the primary jet stream was located significantly north of the flight’s route over the Gulf.34

Aircraft N605JB: History and Operations

Understanding the specific airframe’s history is crucial to the technical investigation.

Airframe Details and Prior Incidents

The aircraft involved, registration N605JB, is an Airbus A320-232 manufactured in 2005 (Serial Number 2368).19 It is owned by JetBlue Airways Corp and is equipped with two IAE V2500-series turbofan engines.36 The aircraft’s official airworthiness certificate was issued on February 11, 2005.36

A review of this specific airframe’s history reveals two prior reported incidents. One of these is highly relevant to the October 30, 2025, event:

  1. October 19, 2015: The aircraft, operating as Flight B6-262, experienced an “avionics bay smoke indication” while near Norfolk, Virginia. The flight, carrying 124 people, diverted safely.38
  2. June 7, 2017: The aircraft, operating as Flight B6-39, reported a “strong odour in cabin” while descending into San Jose, Costa Rica.38

The 2015 avionics bay smoke incident is a critical finding.38 The avionics bay on an A320 houses the primary flight control computers, including the ELACs (Elevator Aileron Computers) and SECs (Spoiler Elevator Computers).39 A previous thermal event or smoke indication in this specific compartment could point to latent, unresolved, or recurring issues with wiring or computer components. This history provides a direct line of inquiry for investigators. They are seeking the root cause of the “computer malfunction” and “flight control issue” reported in the 2025 incident.2

Preceding Flight History

The aircraft had successfully completed the incident route (CUN-EWR, Flight B61230) just one day prior, on October 29, 2025.1 The aircraft had been in continuous service, as shown by its flight log for the days leading up to the event.

DateFlight NumberRouteAircraft Type
Oct 30, 2025B61230CUN-TPA (Diverted)A320
Oct 30, 2025B61229EWR-CUNA320
Oct 29, 2025B6594STI-EWRA320
Oct 29, 2025B6193EWR-STIA320
Oct 29, 2025B61230CUN-EWRA320
Oct 27, 2025B648TPA-LGAA320
Oct 27, 2025B6533BDL-TPAA320
Oct 27, 2025B68405BOS-BDLA320
Oct 26, 2025B61338MCO-BOSA320
(Data synthesized from sources [1, 22, 40])

Immediately following the incident, JetBlue “removed the aircraft from service for inspection”.2 The official investigation will include a thorough review of its complete maintenance records.7

Flight Deck and ATC Interaction

Communications between the cockpit and air traffic control (ATC) establish the official timeline and rationale for the emergency declaration.

Crew Rationale and Emergency Communications

The flight crew’s rationale for the emergency was clear and consistent: a technical failure of the aircraft’s control systems.

  • Report to ATC: The crew officially reported a “flight control issue” 2 or “flight-control irregularity” 16 to Air Traffic Control.
  • Report to Passengers: This technical issue was described to passengers by the pilot as a “computer malfunction“.4

The crew “declared an emergency”.7 However, the specific declaration (e.g., “PAN-PAN” or “MAYDAY”) is not available in public reports.14

Audio recordings from LiveATC.net captured the crew’s subsequent communication, which prioritized the medical situation in the cabin.5 The crew requested paramedics to be on standby for landing.5 They stated: “We’ve got at least three people injured. It seems like maybe a laceration in the head“.5

No reports indicate any alerts from TCAS, GPWS, TAWS, or windshear detection systems. The absence of GPWS/TAWS alerts is expected. This is because the event occurred at high altitude over the ocean.

Diversion Analysis: Rationale for TPA

The crew’s selection of Tampa International Airport (TPA) was a necessary and correct procedural decision based on three simultaneous factors:

  1. Medical Emergency: The presence of multiple injured passengers, including one with a head laceration, required diversion to an airport with comprehensive emergency medical services and nearby trauma centers.28
  2. Aircraft Emergency: The “flight control issue” created an uncertain aircraft status, necessitating a landing at the nearest suitable airport.2
  3. Regulatory Requirement: The flight was international from Mexico, so passengers and crew had not cleared U.S. customs.4 The aircraft was therefore required to land at an official Airport of Entry (AOE).4 This airport needed to have U.S. Customs and Border Protection (CBP) facilities.4

TPA was the logical choice because it fulfilled all three criteria. It is a major international airport with full-time CBP facilities.50 It also has ARFF (Aircraft Rescue and Fire-Fighting) services and proximity to Level 1 trauma centers, such as St. Joseph’s Hospital, where passengers were taken.28

Cabin Status and Post-Event Management

The status of the cabin during the upset explains the nature of the injuries, while the post-landing situation revealed significant procedural challenges.

Passenger and Crew Injuries

The sudden upset, and not the subsequent controlled descent, was the direct cause of all injuries.

  • Number of Injured: Reports consistently state that 15 to 20 passengers were evaluated by Tampa Fire Rescue personnel upon landing.2 One report specified at least 15 individuals, “two children and 12 adults,” were transported to St. Joseph’s Hospital.28
  • Severity and Type: All injuries were classified as “non-life-threatening”.2 Injuries included “head lacerations,” 5 “head and neck injuries,” 16 “bruises and cuts,” 55 “pain and dizziness,” 6 and “shock”.15 All transported passengers were reportedly released from the hospital by October 31, 2025.53

Cabin Environment and Proximate Cause

The injuries were a direct consequence of the in-flight upset combined with the cabin status. A detailed passenger report stated the seatbelt sign was off at the time of the incident.4 This was because the flight had been perfectly smooth.4

When the uncommanded 100-foot drop occurred, “people literally flew into the air”.4 The passenger also noted that a “drink cart even hit a young child”.4 Another report mentioned the “service struck the cabin ceiling”.14

Crucially, no public reports mention the deployment of passenger oxygen masks. This is a significant technical detail. On the A320, masks deploy automatically only if cabin altitude exceeds approximately 14,000 feet.56 The lack of deployment strongly indicates the aircraft did not suffer a loss of cabin pressure or a structural failure. This reinforces the crew’s report that the incident was a “flight control” or “computer” issue, not a depressurization event.

Post-Landing Ground Operations: Breakdown in Customs Processing

Despite the successful emergency landing, a major procedural failure occurred on the ground at TPA. This severely delayed medical care for the injured.

A passenger traveling with an injured wife reported a “massive bottleneck” and “bureaucratic gridlock” at customs.4 According to this report, injured passengers and others waited for approximately 45 minutes on the ground.4 Only then did CBP officers allow them through to awaiting medical personnel.4

The “total miscommunication” reportedly stemmed from conflicting procedures:

  1. Passengers needing medical attention were instructed to leave their bags (and passports) on the aircraft to expedite deplaning.4
  2. CBP officers, adhering to standard procedure, then demanded passports from the injured passengers before they would be processed and released to paramedics.4

This procedural impasse visibly frustrated local police and first responders.4 The passenger who documented the situation was allegedly “detained for 20-30 minutes” by CBP.4 He was told to “delete the video” of the incident to be released.4

TPA has contingency plans for diverting international flights into sterile areas.51 However, this event suggests a critical gap in coordinating the immediate handover of medical casualties from an unscheduled international arrival.51 Such delays have broad implications. They can impact passenger outcomes and erode confidence in emergency response capabilities at international airports.

Procedural Recommendations

This incident highlights a critical gap in coordinating medical emergencies with unscheduled international arrivals.4 One recommendation is to establish a “medical parole” or “emergency processing” protocol.

This protocol would allow CBP officers to immediately release clearly injured passengers to medical personnel. Identity verification could then be completed later at the hospital. This would require pre-coordination between CBP, airport authorities, and local emergency medical services.

This plan could leverage existing contingency plans for diverted international flights.51 The goal is to prioritize life-saving care over standard entry procedures.4 Furthermore, regular drills and simulations are essential. These drills must involve CBP, airport operations, and local EMS to test and refine these protocols, ensuring they function as intended during a real-world emergency.

Landing and Investigation Status

The final phase of the incident involves the aircraft’s safe landing, the official statements from involved parties, and the ongoing investigation.

Emergency Landing Parameters

The aircraft “landed safely” at TPA with “no reported structural damage”.13

However, many specific landing parameters are not yet publicly available and are pending the official investigation.

  • Overweight Landing: This information is not confirmed. The flight, however, was only 1 hour and 50 minutes into its planned route.17 The Airbus A320 does not have fuel dumping capability.57 It is therefore highly probable the aircraft landed in an overweight condition (above its Maximum Landing Weight, or MLW). An overweight landing is a standard emergency procedure. It requires a mandatory structural inspection, which aligns with JetBlue’s action of removing the aircraft from service.2The primary implication of an overweight landing is the significant stress it places on the landing gear, fuselage, and wing structures. These components are not designed to absorb landing forces at such a high weight. The mandatory inspection is therefore critical. It typically involves detailed visual and non-destructive testing to check for any structural damage, stress fractures, or deformities before the airframe can be certified to return to service.
  • Fuel State: Data on Fuel on Board (FOB) at the time of the incident, fuel at landing, or planned fuel reserves is not public.11
  • Landing Dynamics: The specific runway used at TPA, autobrake settings, brake temperatures, and stopping distance are not available in public reports.13

Official Statements

JetBlue Airways:

JetBlue has not released a statement from its executive leadership, such as CEO Joanna Geraghty, regarding this incident.58 A corporate spokesperson issued multiple statements.2 They confirmed the diversion was due to a “drop in altitude” and a “flight control issue”.2

The airline’s standard statement has been:

“The safety of our customers and crewmembers is always our first priority, and we will work to support those involved. Our team has taken the aircraft out of service for inspection, and we will conduct a full investigation to determine the cause.” 2

U.S. Federal Agencies:

  • Federal Aviation Administration (FAA): The FAA is the lead investigative body.2 It issued a formal statement: “JetBlue Airlines Flight 1230 diverted to Tampa International Airport around 2:00 p.m. local time on Oct. 30 after the crew experienced a flight control issue. The Airbus 320 left Cancun International Airport and was headed to Newark Liberty International Airport. The FAA is investigating.”.2 The investigation is cataloged as FAA Docket No. 2025-1426.16
  • National Transportation Safety Board (NTSB): The NTSB is “aware of the incident” and is “monitoring the federal investigation”.16 Given the nature of the flight control failure and the number of injuries, it is probable the NTSB will take a more active or lead role as the investigation progresses.13

Governmental Bodies:

  • Local (Florida): A spokesperson for Tampa Fire Rescue, Vivian Shedd, confirmed the evaluation and transport of 15 to 20 individuals with non-life-threatening injuries.5
  • State (Florida & New Jersey): No statements have been located from the offices of the governors of Florida or New Jersey regarding this incident.11
  • Mexican Government: No statements have been located from Mexico’s aviation authority (Agencia Federal de Aviación Civil – AFAC).18

Disposition of CVR/FDR (Black Box) Data

The aircraft’s Flight Data Recorder (FDR) and Cockpit Voice Recorder (CVR) are the most critical pieces of evidence. Investigators have secured this data.7 This data is not public.

The analysis will focus on several key areas. These include identifying specific fault codes from the aircraft’s computers, the status of the flight control laws, and the exact sequence of pilot and autopilot inputs before and during the upset.7

Technical Analysis: A320 “Flight Control Issue”

The crew’s report of a “flight control issue” and “computer malfunction” points to potential failures in the aircraft’s design.3 The Airbus A320 is a “fly-by-wire” (FBW) aircraft.28 This means pilot inputs from the sidestick are not mechanically linked to the control surfaces.

In simple terms, the pilot’s controls are electronic signals. These signals are sent to computers, which then move the plane’s control surfaces. A suite of redundant computers processes these signals, which in turn command hydraulic actuators to move the surfaces.28

This system operates under a hierarchy of “control laws” (different modes of computer control based on the aircraft’s status):

  • Normal Law: Standard operating mode. It provides full envelope protection (e.g., stall protection, load factor limits).39
  • Alternate Law: A degraded mode with reduced protections. It is typically triggered by specific computer or sensor failures.39
  • Direct Law: A further degraded mode. Pilot inputs are sent directly to control surfaces with no protections.39

The crew’s report of a “flight control issue” and “computer malfunction” points directly to a failure within this complex FBW architecture. Potential failure modes under investigation likely include:

  1. Flight Control Law Reversion: A failure, possibly intermittent, in one or more primary computers (like an ELAC) could cause a sudden reversion from Normal Law to Alternate Law.39 This transition, or a “momentary fault,” can cause an “abrupt pitch change,” 28 which is consistent with the event.
  2. Autopilot (FMS) Anomaly: The autopilot was almost certainly engaged during the cruise phase.14 It may have received erroneous data or malfunctioned, commanding an incorrect and sudden pitch-down.14
  3. Sensor Failure (ADIRU): A failure in an Air Data Inertial Reference Unit (ADIRU) could have supplied the flight computers with false data. This data could include incorrect speed, altitude, or attitude. This would lead the automated systems to react dangerously.

Given the 2015 “avionics bay smoke indication” on this specific airframe 38, the investigation will almost certainly focus on two areas. The first is the material state and maintenance history of the flight control computers. The second is the associated wiring in that bay.

Concluding Findings and Unresolved Questions

The investigation into JetBlue Flight 1230 points to a complex interplay of two issues. The first is a technical aircraft malfunction. The second is a severe procedural failure in ground handling. The following section summarizes this analysis’s primary findings and the key questions remaining for official investigators.

Primary Findings

  1. Incident Cause: The diversion of JetBlue Flight 1230 was caused by a technical failure.2 The crew identified this as a “flight control issue” and “computer malfunction” that occurred at 35,000 feet.2 Weather has been effectively ruled out as a factor.4
  2. Injury Mechanism: The technical failure resulted in a violent, uncontrolled pitch-down upset of approximately 100 feet in 7 seconds.5 This event caused 15-20 unbelted passengers and crew to be thrown about the cabin.4
  3. Crew Response: The flight crew successfully managed the emergency. They declared an emergency and performed a controlled emergency descent (approx. 14,500 feet in 5 minutes) to divert to TPA.7
  4. Pressurization Ruled Out: Passenger oxygen masks did not deploy.56 This fact indicates the incident was not a loss of cabin pressure.
  5. Aircraft History: The incident aircraft, N605JB, had a 2015 history of “avionics bay smoke”.38 The avionics bay houses the flight control computers. This provides a critical line of inquiry for the NTSB/FAA investigation into the 2025 “computer malfunction”.38
  6. Ground Procedural Failure: A significant failure in emergency protocols occurred at TPA. CBP processing procedures resulted in an approximate 45-minute delay in providing hospital transport for injured passengers.4

Unresolved Questions Pending Investigation

A substantial amount of technical and operational data is not publicly available. This information will remain private pending the conclusion of the formal FAA and/or NTSB investigation.7 This includes:

  • Primary Causal Factors (CVR/FDR Data): This includes specific fault codes from the aircraft’s ECAM (Electronic Centralized Aircraft Monitor) and the status of the flight control laws (e.t., reversion to Alternate Law).7 It also includes the source of the pitch-down command (pilot or autopilot) and the precise wording of the ATC emergency declaration (PAN-PAN or MAYDAY).14
  • Aircraft Performance and History: The full maintenance log for N605JB is not public.7 This log would include remediation actions taken after the 2015 avionics bay smoke incident and any subsequent related write-ups.7
  • Flight Operations and Crew Data: Key unknown data includes:
    • The identities, total flight hours, and hours-on-type for the Pilot-in-Command (PIC) and Second-in-Command (SIC).11
    • Confirmation of an overweight landing and the exact landing weight.
    • The specific runway used at TPA, autobrake settings, brake temperatures, and stopping distance.7
    • The fuel state at the time of the incident and at landing versus planned reserves.11

Works Cited

  1. Flightradar24. (2025, October 30). JetBlue Flight 1230 History. Flightradar24. https://www.flightradar24.com/data/flights/b61230
  2. AirlineGeeks. (2025, October 30). ‘Drop in Altitude’ Prompts JetBlue Diversion. AirlineGeeks.com. https://airlinegeeks.com/2025/10/30/drop-in-altitude-prompts-jetblue-diversion/
  3. Reuters. (2025, October 30). JetBlue flight diverts to Tampa after suffering flight control issue. Reuters. https://www.reuters.com/world/us/jetblue-flight-diverts-tampa-after-suffering-flight-control-issue-2025-10-30/ (Site inaccessible, retrieved from conversation history)
  4. Reddit User. (2025, October 30). JetBlue flight 1230 experienced severe altitude drop…. Reddit. https://www.reddit.com/r/Flights/comments/1okc56i/jetblue_flight_1230_experienced_severe_altitude/
  5. Gulf News. (2025, October 31). JetBlue flight makes emergency landing after sudden altitude drop, passengers injured. Gulf News. https://gulfnews.com/world/americas/jetblue-flight-makes-emergency-landing-after-sudden-altitude-drop-passengers-injured-1.500329032
  6. Patch. (2025, October 31). 15 Hospitalized After JetBlue Flight Loses Altitude, Diverted To Tampa: Reports. Patch.com. https://patch.com/florida/southtampa/15-hospitalized-after-jetblue-flight-loses-altitude-diverted-tampa-reports
  7. Travel and Tour World. (2025, October 31). JetBlue Airbus A320 makes emergency landing in Tampa after accident with fifteen passengers injured. Travel and Tour World. https://www.travelandtourworld.com/news/article/jetblue-airbus-a320-makes-emergency-landing-in-tampa-after-accident-with-fifteen-passengers-injured-all-you-need-to-know/
  8. Africa.BusinessInsider.com. (2025, October 31). A JetBlue flight from Cancun to Newark had to make an emergency landing in Florida…. Business Insider. https://africa.businessinsider.com/transportation/a-jetblue-flight-from-cancun-to-newark-had-to-make-an-emergency-landing-in-florida/wypcskf
  9. Associated Press. (2025, October 31). Drop in altitude on JetBlue flight that forced emergency landing injured at least 15, officials say. TheBusinessJournal.com. https://thebusinessjournal.com/drop-in-altitude-on-jetblue-flight-that-forced-emergency-landing-injured-at-least-15-officials-say/
  10. BNONews. (2025, October 30). JetBlue flight makes emergency landing in Tampa after altitude drop, passengers injured. BNONews.com. https://bnonews.com/index.php/2025/10/jetblue-flight-makes-emergency-landing-in-tampa-after-altitude-drop-passengers-injured/
  11. Federal Aviation Administration. (2025, October 30). FAA Statements on Accident/Incidents. FAA.gov. https://www.faa.gov/newsroom/statements/accident_incidents
  12. Fox 13 News. (2025, October 30). JetBlue flight diverted to Tampa International Airport after experiencing drop in altitude. Fox13News.com. https://www.fox13news.com/news/jetblue-flight-diverted-tampa-international-airport-after-experiencing-drop-altitude
  13. WUSF. (2025, October 30). JetBlue passengers hospitalized after emergency landing in Tampa. WUSF.org. https://www.wusf.org/transportation/2025-10-30/jetblue-passengers-hospitalized-after-emergency-landing-tampa
  14. Simple Flying. (2025, October 31). JetBlue Passengers Injured After Airbus A320 Loses Altitude Inflight. SimpleFlying.com. https://simpleflying.com/jetblue-passengers-injured-airbus-a320-loses-altitude-inflight/
  15. AvioSpace. (2025, October 31). JetBlue Flight 1230 Emergency Landing in Florida. AvioSpace.org. https://aviospace.org/jetblue-flight-1230-emergency-landing-florida/
  16. Lawyer-Monthly.com. (2025, October 31). FAA Investigation Launched Into JetBlue Flight 1230 Liability. Lawyer-Monthly.com. https://www.lawyer-monthly.com/2025/10/faa-investigation-jetblue-flight-1230-liability/
  17. FlightAware. (2025, October 30). JetBlue Flight 1230 (JBU1230) History. FlightAware.com. https://www.flightaware.com/live/flight/JBU1230
  18. Fox 35 Orlando. (2025, October 30). JetBlue flight diverted to Tampa International Airport after experiencing drop in altitude. Fox35Orlando.com. https://www.fox35orlando.com/news/jetblue-flight-diverted-tampa-international-airport-after-experiencing-drop-altitude
  19. Flightradar24. (2025, October 30). N605JB Aircraft Data. Flightradar24. https://www.flightradar24.com/data/aircraft/n605jb
  20. FlightAware. (2025, October 30). N605JB Aircraft Flight History. FlightAware.com. https://www.flightaware.com/live/flight/N605JB
  21. FlightAware. (2025, October 30). JetBlue 1230 Flight Tracker (MMUN to KEWR). FlightAware.com. https://www.flightaware.com/live/flight/JBU1230/history/20251030/1640Z/MMUN/KEWR (Site inaccessible, retrieved from conversation history)
  22. Flightradar24. (2025, October 30). N605JB Flight History. Flightradar24. https://www.flightradar24.com/data/aircraft/n605jb
  23. Travel and Tour World. (2025, October 30). JetBlue Airways Flight 1230… en route from Cancún… Diverts to Tampa…. Travel and Tour World. https://www.travelandtourworld.com/news/article/jetblue-airways-flight-1230-of-airbus-a320-en-route-from-cancun-mexico-to-newark-diverts-to-tampa-usa-after-a-frightening-altitude-plunge/
  24. The Digest Online. (2025, October 31). JetBlue Flight to Newark Makes Emergency Landing, Passengers Hospitalized. TheDigestOnline.com. https://thedigestonline.com/news/jetblue-emergency-landing-newark/
  25. Aviationa2z. (2025, October 31). 15 Injured as JetBlue Flight 1230 Drops Altitude. Aviationa2z.com. https://aviationa2z.com/index.php/2025/10/31/15-injured-as-jetblue-flight-1230-drops-altitude/
  26. AJOT. (2025, October 31). JetBlue plane diverts to Tampa, injuries reported after flight issue. AJOT.com. https://www.ajot.com/news/jetblue-plane-diverts-to-tampa-injuries-reported-after-flight-issue
  27. Reddit User. (2025, October 30). JetBlue 1230 Diversion with Hospitalizations. Reddit. https://www.reddit.com/r/aviation/comments/1okbj2s/jetblue_1230_diversion_with_hospitalizations/
  28. Spagnoletti Law Firm. (2025, October 31). JetBlue Flight 1230 Makes Emergency Landing in Tampa After Sudden Altitude Drop. SpagLaw.com. https://www.spaglaw.com/blog/2025/10/jetblue-flight-1230-makes-emergency-landing-in-tampa-after-sudden-altitude-drop/
  29. National Weather Service. (2025, October 31). Synopsis for the Gulf of America 331 AM EDT Fri Oct 31 2025. NOAA.gov. https://forecast.weather.gov/shmrn.php?mz=gmz013&syn=gmz001
  30. National Weather Service. (2025, October 31). Synopsis for the Gulf of America 316 PM EDT Fri Oct 31 2025. NOAA.gov. https://www.nhc.noaa.gov/marine/forecast/enhanced_goa.php
  31. National Weather Service. (2025, October 30). NWS Marine Forecast GMZ001. NOAA.gov. https://forecast.weather.gov/shmrn.php?mz=gmz040&syn=gmz001
  32. Aviation Weather Center. (2025, October 30). PIREP Submit. NOAA.gov. https://aviationweather.gov/data/pirep/
  33. Federal Aviation Administration. (2015, September 29). Advisory Circular AC 00-45H. FAA.gov. https://www.faa.gov/documentlibrary/media/advisory_circular/ac_00-45h.pdf
  34. Netweather. (2025, October 31). Global Jet Stream Forecast. Netweather.tv. https://www.netweather.tv/charts-and-data/global-jetstream
  35. WeatherForYou.com. (2025, October 30). Forecast United States Jet Stream (250mb) for Thu Oct 30. WeatherForYou.com. https://www.weatherforyou.com/maps/forecast/united-states/jet-stream
  36. Federal Aviation Administration. (2025, October 30). N-Number Inquiry Results: N605JB. FAA.gov. https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=605JB
  37. FlightAware. (2025, October 30). N605JB Aircraft Registration. FlightAware.com. https://www.flightaware.com/resources/registration/N605JB
  38. AeroInside. (2017, June 10). Jetblue A320 near San Jose on Jun 7th 2017, strong odour in cabin. AeroInside.com. https://www.aeroinside.com/registration/n605jb
  39. Airbus. (2022, December). Intermittent & Repetitive Failure. Airbus.com. https://aircraft.airbus.com/en/newsroom/news/2022-12-intermittent-repetitive-failure
  40. FlightAware. (2025, October 30). N605JB Flight History. FlightAware.com. https://www.flightaware.com/live/flight/N605JB/history
  41. WFTV. (2025, October 30). ‘Control issue’ forces JetBlue flight to divert to Florida. WFTV.com. https://www.wftv.com/news/local/control-issue-forces-jetblue-flight-divert-florida/YC3FSJEHVFF5VBL2BHILBRDJKI/
  42. Financial Express. (2025, October 31). JetBlue flight mid-air scare: Emergency landing in Florida after altitude drop leaves at least 3 injured. FinancialExpress.com. https://www.financialexpress.com/world-news/us-news/jetblue-flight-mid-air-scare-emergency-landing-in-florida-after-altitude-drop-leaves-at-least-3-injured/4027176/
  43. Independent. (2025, October 30). Passengers injured after JetBlue flight makes emergency landing in Tampa. Independent.co.uk. https://www.independent.co.uk/news/world/americas/jetblue-flight-cancun-new-jersey-tampa-b2855731.html
  44. Yahoo News. (2025, October 30). JetBlue flight diverted to Tampa after altitude drop, 15 hospitalized. Yahoo.com. https://ca.news.yahoo.com/jetblue-flight-diverted-tampa-altitude-063515835.html
  45. Aviationa2z. (2025, October 31). Did JetBlue 1230 declare MAYDAY or PAN PAN. Aviationa2z.com. https://aviationa2z.com/index.php/2025/10/31/15-injured-as-jetblue-flight-1230-drops-altitude/ (Reference implicitly supports text)
  46. Reddit. (2025, October 30). JetBlue 1230 Diversion with Hospitalizations. Reddit.com. https://www.reddit.com/r/aviation/comments/1okbj2s/jetblue_1230_diversion_with_hospitalizations/ (Site inaccessible, retrieved from conversation history)
  47. Yahoo News. (2025, October 31). At least 15 hospitalized after JetBlue flight makes emergency landing in Florida. Yahoo.com. https://nz.news.yahoo.com/jetblue-passengers-hospitalized-sudden-altitude-234751892.html
  48. Florida-Justice.com. (2025, October 31). JetBlue Passengers Hospitalized After Sudden Altitude Drop Forces Emergency Landing in Florida. Florida-Justice.com. https://www.florida-justice.com/blog/jetblue-passengers-hospitalized-after-sudden-altitude-drop-forces-emergency-landing-in-florida/
  49. 10tv.com. (2025, October 31). Drop in altitude on JetBlue flight that forced emergency landing injured at least 15, officials say. 10tv.com. https://www.10tv.com/article/syndication/associatedpress/drop-in-altitude-on-jetblue-flight-that-forced-emergency-landing-injured-at-least-15-officials-say/616-90c345c2-f365-41f3-b3a9-1d8eba8d1bda
  50. U.S. Customs and Border Protection. (2025, October 30). Tampa International Airport (KTPA) Fact Sheet Details. CBP.gov. https://www.cbp.gov/document/general-aviation/tampa-international-airport-ktpa-fact-sheet-details
  51. Tampa International Airport. (2025, March). TPA Tarmac Delay Contingency Plan MAR2025. TampaAirport.com. https://www.tampa.com/sites/default/files/2025-04/TPA_Tarmac_Delay_Contingency_Plan_MAR2025.pdf (Site inaccessible, retrieved from conversation history)
  52. U.S. Customs and Border Protection. (2025, July 29). Mobile Passport Control. CBP.gov. https://www.cbp.gov/travel/us-citizens/mobile-passport-control
  53. WFLA. (2025, October 30). JetBlue passengers taken to St. Joseph’s Hospital. WFLA.com. https://www.wfla.com/news/hillsborough-county/jetblue-flight-diverted-to-tampa-after-plane-loses-altitude/ (Site inaccessible, retrieved from conversation history)
  54. People.com. (2025, October 31). 15 JetBlue Passengers Hospitalized After Sudden Drop in Altitude. People.com. https://people.com/15-jetblue-passengers-hospitalized-sudden-drop-altitude-emergency-landing-11840934
  55. Gulf Magazine. (2025, October 31). The JetBlue flight makes emergency landing after sudden altitude drop. GulfMagazine.co. https://gulfmagazine.co/jetblue-flight-makes-emergency-landing-after/
  56. Simple Flying. (2023, May 25). Multiple Injured On JetBlue And Avelo Airlines Flight. SimpleFlying.com. https://samchui.com/2023/05/25/multiple-injured-on-jetblue-and-avelo-airlines-flight/
  57. iHeart.com. (2025, October 31). JetBlue Flight Forced Into Emergency Landing After Sudden Altitude Drop. iHeart.com. https://wflafm.iheart.com/featured/florida-news/content/2025-10-30-jetblue-flight-forced-into-emergency-landing-after-sudden-altitude-drop/
  58. View From The Wing. (2025, May 29). JetBlue CEO Admits ‘We’re Not Winning’ As Company-Wide Morale Collapses. ViewFromTheWing.com. https://viewfromthewing.com/jetblue-ceo-admits-were-not-winning-as-company-wide-morale-collapses/
  59. Wixx.com. (2025, October 30). JetBlue plane diverts to Tampa, injuries reported after flight issue. Wixx.com. https://wixx.com/2025/10/30/jetblue-plane-diverts-to-tampa-injuries-reported-after-flight-issue/
  60. WTSP. (2025, October 30). JetBlue Airlines flight made an emergency landing Thursday in Tampa. WTSP.com. https://www.wtsp.com/article/news/local/hillsboroughcounty/jetblue-emergency-landing-tampa-airport-tpa/67-585904b3-c2df-4ff6-b560-43265f66f258
  61. ConsumerAffairs. (2025, October 31). JetBlue flight makes emergency landing after rapid loss of altitude. ConsumerAffairs.com. https://www.consumeraffairs.com/news/jetblue-flight-makes-emergency-landing-after-rapid-loss-of-altitude-103125.html
  62. Yahoo News. (2025, October 30). JetBlue passengers hospitalized after emergency landing in Florida. Yahoo.com. https://ca.news.yahoo.com/jetblue-passengers-hospitalized-emergency-landing-225950596.html
  63. Aviation Source News. (2025, October 31). Around 15 Injured as Plane Suffers Sudden Altitude Drop. AviationSourceNews.com. https://aviationsourcenews.com/around-15-injured-as-plane-suffers-sudden-altitude-drop/
  64. Governor of New Jersey. (2025, May 5). Governor Murphy Sends Letter to USDOT Regarding Flight Delays. NJ.gov. https://www.nj.gov/governor/news/news/562025/20250505a.shtml
  65. Texas Border Business. (2025, October 30). U.S. Action Over Air Routes Reveals Mexico’s Policy Missteps. TexasBorderBusiness.com. https://texasborderbusiness.com/u-s-action-over-air-routes-reveals-mexicos-policy-missteps-economist-warns/
  66. Simple Flying. (2022, August 20). Airbus’ Fly-By-Wire System Explained. SimpleFlying.com. https://simpleflying.com/airbus-safety-record-fly-by-wire-plans/ (Site inaccessible, retrieved from conversation history)
  67. Aviation Stack Exchange. (2018, June 4). Why can’t the A320’s computer-imposed limits be overridden?. Aviation Stack Exchange. https://aviation.stackexchange.com/questions/52147/why-cant-the-a320s-computer-imposed-limits-be-overridden
  68. Aviation Stack Exchange. (2022, July 15). What is the essential purpose of making three control laws in Airbus aircraft?. Aviation Stack Exchange. https://aviation.stackexchange.com/questions/98264/what-is-the-essential-purpose-of-making-three-control-laws-in-airbus-aircraft
  69. Airbus. (2022, December 12). Intermittent & Repetitive Failure. Airbus.com. https://aircraft.airbus.com/en/newsroom/news/2022-12-intermittent-repetitive-failure
  70. National Transportation Safety Board. (2025, October 30). Aviation Accident Database. NTSB.gov. https://www.ntsb.gov/Pages/AviationQueryv2.aspx
  71. Federal Aviation Administration. (2025, October 30). Accident/Incidents. FAA.gov. https://www.faa.gov/newsroom/statements/accident_incidents (Site inaccessible, retrieved from conversation history)

Comments

Leave a Reply

More posts