airtraffic

Recent Posts

Pages: 1 [2] 3 4 ... 10
11
https://airlive.net/tracking/2025/12/16/delta-flight-dl405-taxied-during-3-hours-after-landing-before-finally-reaching-the-gate-at-jfk/

(I've been listening to it, and they were on 121.65, so not the best audio.  It was very busy on both ground freqs
several crews timed out, will work on cleaning it up, but the taxi seemed longer than the flight :) )

New York, NY – Passengers aboard a Delta Air Lines flight arriving at John F. Kennedy International Airport (JFK) on Sunday, December 14, 2025, faced an extraordinarily long delay after landing, with the aircraft spending nearly three hours taxing to its gate.

Delta Flight DL405, a scheduled service from San Francisco, was operated by a Boeing 767-300 aircraft, registration N193DN. The flight landed on JFK’s Runway 31R at 16:29 local time, nearly one hour behind its scheduled arrival time.

However, the journey was far from over for the passengers. Following touchdown, the aircraft began a lengthy and highly unusual taxi to its assigned terminal. The flight finally reached Gate B37 an astonishing 2 hours and 58 minutes after landing according to FlightRadar24.   The three-hour delay on the ground highlights significant operational challenges at JFK on Sunday. While long taxi times are not uncommon during peak traffic or severe weather, a duration nearing three hours from runway to gate is highly unusual for a major airport and would represent a frustrating experience for all passengers and crew involved.

Delta Air Lines has not yet provided an official explanation for the extensive delay, but severe congestion or an unexpected closure of taxiways likely contributed to the extended hold. 
12
Yes, indeed lol!
13
yes 13.4 hours of fuel would be a lot for Atlanta  :-D
14
ok thanks - actually wasn't sure on the fuel I just assumed so I'll update it to just the quote.
15
Good catch... one note though, regarding the fuel remaining, I'm fairly certain they meant 13,400 LBS of fuel was remaining 😊
16
Monday 12/15/25

~17:40Z (12:40pm local) - FFT2467 Airbus A321neo from CLE to ATL calls Mayday on departure from Rwy 24L, stating failure in Engine #1.  Levels off @ 3000ft for return to field.  "188 souls on board, fuel on board 13.4".

Later reports both engines available but maintains emergency status.  "no remaining deficiencies but did have that compressor stall and expect some potential to lose engine 1 again"... "not sure if we hit a bird or what the problem was on that engine 1 ... you may want to look for shrapnel and/or bird pieces, we had no indications and no sign of anything".

24L was closed for FOD inspection (none found); various flights on approach were given delay vectors and set up for 24R, but switched back to 24L, once that runway reopened and FFT2467 inbound for 24R.

~17:49Z FFT2467 reported ready to return to CLE, given turns back to the field and cleared for ILS 24R approach.

~17:58Z FFT2467 landed safely back at CLE on 24R, cleared runway onto taxiway N holding short 24L, remained with Tower frequency, shut down engine 1 for inspection.  Pilot confirmed no indication of fire so no oxygen was deployed in cabin or cockpit.  Once cleared for return to gate FFT2467 reported a brake fault which delayed movement back to the gate area until 18:16Z, switched to Ground after clearing 24L then waited for tug to help with right turn into the gate.

Combination KCLE Twr/Departure/Ground from 1737Z - 1826Z, edited for time and content, not realtime.


https://www.faa.gov/newsroom/statements/accident_incidents
December 15, 2025
Commercial Aviation / Cleveland, Ohio
Frontier Airlines Flight 2467 returned safely to Cleveland Hopkins International Airport in Ohio around 1 p.m. local time on Monday, Dec. 15, after the crew reported an engine issue. The Airbus A321 was headed to Hartsfield-Jackson Atlanta International Airport. The FAA will investigate. Please contact the airline for additional information. 
17
Dec 12, 2025, approx. 2101z

Unidentified USAF air-to-air refueller, involved in US government operations in waters off of Venezuela, nearly collides with JetBlue A320 (Reg. N809JB) operating JBU1112 flight from Curaçao to New York; who then reported having to slow their climb and, understandably, were not happy.

Transmission from TNCC Curaçao Control. An Air Canada flight to Montreal (AC1355) had been only about a minute in front, but was then some distance north-west of the JetBlue flight.

Another source:
https://www.aeroinside.com/21382/jetblue-a320-near-curacao-on-dec-12th-2025-near-collision-with-invisible-us-military-aircraft
18
Saturday 12/13/25 17:35Z (12:35pm local) - UAL803 Heavy (Boeing 777-200) from IAD to Tokyo, declares Mayday on takeoff from Rwy 1C for left engine failure.  290 persons on board, 16 hours of fuel.  Remained with Tower in a low altitude climb, before accepting vectors to the South then switch to Departure.

(According to social media the captain notified passengers it was a bird strike, tho this has not been confirmed by FAA or other reporting).

Dulles Operations subsequently requested 1C/19C closed due to smoke, later reported 6-7 areas of fire and "seeing pieces out here".  AAL2149 on final for 01C had approach clearance switch to 01R.

UAL803 climbed to 5k ft and entered a hold south of IAD for return on ILS approach to 1R; dumped fuel down to ~10 Hours / 146k pounds of fuel.

UAL803 landed 1R, stopped on the runway reporting possible blown tire, and switched to emergency frequency 123.775 (not on LiveATC)

Attached combination KIAD 1L/1C Twr, KIAD App IADFE (125.8), KIAD 1R Twr (120.1); edited for time and content, not realtime etc.

Timeline (Z):

17:33.30   UAL803 cleared for takeoff Rwy 1C
17:35.40   UAL803 declares mayday - "lost an engine going straight out". 
17:36.23   UAL803 advised of low altitude alert @ 1000ft in slow climb.  Remains on runway heading and on Tower frequency - "I'm busy"... "TWR: can you accept a vector" - "Negative"
17:38.03   UAL803 advised of MVA 2000ft - "we're climbing"
17:39.15   UAL803 starts turn back to the South
17:42.24   UAL803 switch to Departure (125.8)
17:42.40   IAD Ops requests closure of 1C due to smoke - "about 6-7 areas here that are [inaudible] fires... seeing pieces out here as well"
17:46.18   UAL803 confirms left engine loss; "dumping fuel right now"
17:49.15   UAL803 given instructions to proceed direct EERRS hold southbound on the 1R localizer, maintaining 5k with 10-15mi legs at their discretion
18:05.30   UAL803 reports done with fuel jettison, fuel status "over 10 hours / 146k pounds"
18:07.40   UAL803 reports ready to turn inbound on ILS approach for 1R
18:11.30   UAL803 cleared for ILS approach 1R.   
18:15.00   UAL803 switch to Tower (120.1)
18:19.30   UAL803 rolling out on Rwy 1R, informs Tower will stop on runway - "may have a blown tire"
18:20.45   UAL803 switches to emergency frequency 123.775

Links/Media

https://flightaware.com/live/flight/UAL803/history/20251213/1730Z/KIAD/RJTT

https://www.reddit.com/r/aviation/comments/1plsh4y/united_803_a_b777_departing_washington_dulles_for/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

https://avherald.com/h?article=5311d112&opt=0
A United Boeing 777-200, registration N78004 performing flight UA-803 from Washington Dulles,DC (USA) to Tokyo Haneda (Japan) with 275 passengers and 15 crew, was climbing out of Dulles' runway 01C when the crew declared Mayday Mayday Mayday reporting they had lost the left hand engine (GE90). Smoke developed at the side of the runway prompting emergency services to respond, a small grass fire was extinguished. The aircraft stopped the climb at 5000 feet and entered a hold dumping fuel, then returned to runway 01R for a safe landing about 45 minutes after departure.

https://www.faa.gov/newsroom/statements/accident_incidents
December 13, 2025
Commercial Aviation / Dulles, Virginia
United Airlines Flight 803 safely returned to Dulles International Airport in Virginia around 1:20 p.m. local time on Saturday, Dec. 13, after experiencing an engine failure during departure. The FAA will investigate. The Boeing 777-200 was travelling to Tokyo, Japan. Contact the airline for additional information.


https://www.asias.faa.gov/apex/f?p=100:96:13205540296846::::P96_ENTRY_DATE,P96_MAKE_NAME,P96_FATAL_FLG:15-DEC-25,BOEING
AIRCRAFT NO. 1 ENGINE AND ENGINE COWLING SEPARATED AND CAUGHT FIRE ON DEPARTURE, RETURNED TO IAD, CHANTILLY, VA.
19
Feed Setup Pictures / Re: Not getting answer from LiveATC
« Last post by dave on December 12, 2025, 14:09:03 UTC »
Your ticket was misfiled in our system. We will get back to you today.
20
Feed Setup Pictures / Not getting answer from LiveATC
« Last post by Norwetec on December 12, 2025, 13:58:36 UTC »
Hi i have a big settup with 12 radioes that me and Live ATC have been chatting about. I am ready now but no answer from them. How do we contact them?
Pages: 1 [2] 3 4 ... 10