Another Runway Incursion at KDCA
Not so. I'm not in the USA and don't have a problem. Here's the video from that linked story:
Last edited by TWT; 30th May 2024 at 08:39.
I can't access the article either - in UK. But watching the video, it looks like LAHSO may have been in use, and the almost inevitable result of those procedures when the AHS bit is overlooked or the landing doesn't go as planned. The likely alternative is simply an ATC error when using crossing runways. As ever, the investigation will tell us more and it will be interesting to see what led up to it going wrong. Despite the US shifting huge numbers of aircraft every day, another runway incident raises a question, less about the investigations into incidents but more about doing something to prevent re-occurrence.
I can't access the article either - in UK. But watching the video, it looks like LAHSO may have been in use, and the almost inevitable result of those procedures when the AHS bit is overlooked or the landing doesn't go as planned. The likely alternative is simply an ATC error when using crossing runways. As ever, the investigation will tell us more and it will be interesting to see what led up to it going wrong. Despite the US shifting huge numbers of aircraft every day, another runway incident raises a question, less about the investigations into incidents but more about doing something to prevent re-occurrence.
Thread Starter
https://www.facebook.com/share/v/XNE...ibextid=w8EBqM
https://www.nbcboston.com/news/local...rport/3384166/
The AA A319 did a high speed RTO (~80 kts) and the poor King Air pilot ordered to go around was already on the ground, probably in reverse thrust. What's scary here is that this keeps happening!
https://www.nbcboston.com/news/local...rport/3384166/
The AA A319 did a high speed RTO (~80 kts) and the poor King Air pilot ordered to go around was already on the ground, probably in reverse thrust. What's scary here is that this keeps happening!
The following 2 users liked this post by Lake1952:
Seems now it is just a matter of time !
At the time of the incident, the local controller (LC) was handling runway 4 departures, runway 1 arrivals and departures, and runway 33 arrivals and departures.
King Air 250AA was issued a runway 33 landing clearance with an RJ LUAW on 33. The RJ was then issued “immediate takeoff” with the King Air on a 2 mi final.
AA 2134 was issued a takeoff clearance for runway 1 with company traffic called on a 4-mile final for runway 1. No mention of the landing traffic on runway 33 because I suspect the LC just forgot about the landing traffic.
Regarding post #4, there were no LAHSO ops in effect.
Runway 1/19 at DCA is listed as the busiest runway in the U.S. at 819 ops per day.
The recent FAA Authorization Bill added 5 slots to DCA.
King Air 250AA was issued a runway 33 landing clearance with an RJ LUAW on 33. The RJ was then issued “immediate takeoff” with the King Air on a 2 mi final.
AA 2134 was issued a takeoff clearance for runway 1 with company traffic called on a 4-mile final for runway 1. No mention of the landing traffic on runway 33 because I suspect the LC just forgot about the landing traffic.
Regarding post #4, there were no LAHSO ops in effect.
Runway 1/19 at DCA is listed as the busiest runway in the U.S. at 819 ops per day.
The recent FAA Authorization Bill added 5 slots to DCA.
The following users liked this post:
