ARFF Daily News
Published on:
Friday the 19th of April, 2024
Collision narrowly avoided at Reagan National Airport after two planes cleared onto the same runway
By Gregory Wallace and Pete Muntean, CNNWire
The Federal Aviation Administration is investigating how two jetliners were put on an apparent collision course as they were leaving Reagan National Airport Thursday morning, prompting air traffic controllers to frantically radio each plane to stop.
Air traffic control audio recordings detail controllers shouting for a JetBlue flight to stop its takeoff run as a Southwest Airlines flight began taxiing across the runway in front of it.
The two planes stopped about 400 feet apart, according to data compiled by FlightRadar24, which also shows at least the "forward fuselage" of the Southwest flight had entered the runway.
A controller responsible for the runways at Reagan National had cleared the JetBlue Airways flight to take off at about 7:40 a.m., the recordings from LiveATC.net showed. At around the same time, a controller responsible for taxiing aircraft directed a Southwest Airlines jet across the same runway.
About 30 seconds after clearing the JetBlue plane, the controllers shouted for both planes to stop.
"JetBlue 1554 stop! 1554 stop!" the tower controller called out.
"2937 stop!" the ground controller ordered.
The Southwest pilot replied: "We stopped. We were cleared to cross Runway 4."
The FAA said it will investigate the incident and acknowledged in a statement to CNN that both planes were sent onto the runway.
"An air traffic controller instructed Southwest Airlines Flight 2937 to cross Runway 4 at Ronald Reagan Washington National Airport while JetBlue Flight 1554 was starting its takeoff roll on the same runway," the FAA said.
Following the incident, the JetBlue plane taxied back to the runway threshold and then took off for Boston Logan.
"Do you have room to get around the Southwest or even double back on Runway 4 full length?" the controller asked.
"Looks like we can make a left on Alpha, JetBlue 1554," the pilot replied.
The Southwest plane was directed to continue across that runway and taxi toward a second runway, where it took off as planned, bound for Orlando.
JetBlue said its Boston-bound flight "aborted take-off due to another aircraft attempting to cross the runway." The plane was inspected and then departed safely, the airline said.
"We are aware of the incident and are working with the FAA to fully understand the circumstances," Southwest Airlines told CNN.
CNN has reached out to the National Transportation Safety Board to see if it plans to investigate the incident.
Delta flight from Savannah to Atlanta declares emergency before landing
The passengers and crew were aboard a Boeing 757-200.
Author: Reeves Jackson
ATLANTA — A Delta flight bound from Savannah to Atlanta declared an emergency before making its landing at Hartsfield-Jackson International Airport on Thursday, according to a spokesperson with the airline.
The flight crew aboard Delta Flight 2728, a Boeing 757-200, noticed what is called a "flap disagree" while up in the air. According to a Delta spokesperson, the issue occurs when the plane’s flaps become misaligned.
The flight crew then issued an emergency alert with Air Traffic Control to get priority landing. The pilots landed the plane safely and taxied to the gate as normal.
"This is an uncommon occurrence but is a part of extensive flight crew training to manage through safely," a Delta spokesperson said, adding, "Nothing is more important than the safety of our customers and people."
A Boeing 757-200 holds 199 passengers.
https://www.11alive.com/article/travel/delta-flight-emergency-before-landing-atlanta/85-78c19a24-7900-4b1a-9645-aa37b2704717
NTSB Final Report: Luscombe 8A
Surveillance Cameras Recorded The Airplane Depart The Runway Surface, Bounce, And Impact A Hangar
Location: Boerne, Texas Accident Number: CEN23LA426
Date & Time: September 28, 2023, 06:31 Local Registration: N71804
Aircraft: Luscombe 8A Aircraft Damage: Substantial
Defining Event: Loss of control on ground Injuries: 1 Minor
Flight Conducted Under: Part 91: General aviation - Personal
Analysis: The pilot reported that during the landing roll his feet become entangled in the rudder pedals and he inadvertently applied brake pressure. The airplane veered left and the pilot unsuccessfully attempted to regain directional control with opposite rudder and increased engine power.
Airport surveillance cameras recorded the airplane depart the runway surface, bounce, and impact a hangar, which resulted in substantial damage to both wings and the fuselage. The pilot did not return the National Transportation Safety Board 6120.1/2 form.
Probable Cause and Findings: The National Transportation Safety Board determines the probable cause(s) of this accident to be -- The pilot’s failure to maintain directional control during the landing roll.
FMI: www.ntsb.gov
Today in History
24 Years ago today: On 19 April 2000 an Air Philippines Boeing 737-200 crashed on approach to Davao; killing all 131 on board.
Date: Wednesday 19 April 2000
Time: 07:00
Type: Boeing 737-2H4
Owner/operator: Air Philippines
Registration: RP-C3010
MSN: 21447/508
Year of manufacture: 1978
Total airframe hrs: 68475 hours
Cycles: 79522 flights
Engine model: Pratt & Whitney JT8D-9A
Fatalities: Fatalities: 131 / Occupants: 131
Aircraft damage: Destroyed, written off
Category: Accident
Location: 8 km NE of Davao City-Francisco Bangoy International Airport (DVO) - Philippines
Phase: Approach
Nature: Passenger - Scheduled
Departure airport: Manila-Ninoy Aquino International Airport (MNL/RPLL)
Destination airport: Davao City-Francisco Bangoy International Airport (DVO/RPMD)
Confidence Rating: Information is only available from news, social media or unofficial sources
Narrative:
Air Philippines Flight 541, a Boeing 737-200, departed Manila (MNL) at 05:21 hours and was due to land at Davao (DVO), Philippines, around 06:45.
The aircraft was being flown as a route check for a captain. Another captain was acting as Pilot Monitoring on the flight. The en route part of the flight was uneventful. The aircraft was conducting an ILS approach to runway 05 and the controller reported that they would be behind Philippine Airlines flight 809, an Airbus A319.
As the Boeing 737 broke out of clouds, the A319 was observed on runway 05. The Pilot Flying informed ATC of his intention to perform a 360° maneuver, but the Pilot Monitoring advised ATC of the opposite, stating that the aircraft would turn right instead of following the missed approach procedure, which called for a left hand turn to a 020° heading. The aircraft re-entered clouds and attempted to fly visually at a lower altitude in instrument conditions when in fact it should have climbed to 4000 feet.
The flight continued over Samal Island and the flight requested a VOR/DME approach and landing in the opposite direction (runway 23), which was approved by the controller. After having aligned with the runway heading, the aircraft descended below the normal glide path for this approach. It continued down to 570 feet at a point where the aircraft should have been at 1500 feet.
The aircraft crashed into a coconut plantation on a hillside in Barangay San Isidro, disintegrated and caught fire.
Mailing Address
Subscribe to our newsletter
Contact Us
We will get back to you as soon as possible.
Please try again later.