Page Links: Index Page
| captains_log
January 30, 2025, 12:37:00 GMT permalink Post: 11817194 |
Could it be this becomes another case that the regulatory defined airplane exterior (including landing light) lighting (especially for small RJ) is simply insufficient to let it stand out in the airport / city Xmas tree of lighting?
And the chopper crew simply had the next airplane in sequence of landing in sight and not the one they collided with? RIP Akin to allowing a car to drive across a motorway/highway should just never be permissible ever. Overpass or underpass only unless emergency. Some other observations
Condolences to all involved, and their families, and the teams that will be involved in the recovery. Last edited by captains_log; 30th January 2025 at 13:17 . Subjects
ATC
Blackhawk (H-60)
Route Altitude
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| EFHF
January 30, 2025, 17:27:00 GMT permalink Post: 11817434 |
In any case there could not have been any reasonable horizontal separation even if the helo flew within the helo route altitude restrictions. TWR gave instructions for lateral separation with this call:
PAT25,
pass behind
the CRF.
Last edited by EFHF; 30th January 2025 at 18:00 . Reason: Error in TDZ location corrected, AGL was 175 ft before correction Subjects
PAT25
Pass Behind
Pass Behind (All)
Pass Behind (PAT25)
Route Altitude
Separation (ALL)
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| Lonewolf_50
February 05, 2025, 14:41:00 GMT permalink Post: 11822257 |
So it wasn't just me. Last edited by Lonewolf_50; 6th February 2025 at 13:20 . Subjects
Blackhawk (H-60)
Route Altitude
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| safetypee
March 11, 2025, 20:35:00 GMT permalink Post: 11845640 |
"Near Midair Collision Events at DCA Review of information gathered from voluntary safety reporting programs along with FAA data regarding encounters between helicopters and commercial aircraft near DCA from 2011 through 2024 indicated that a vast majority of the reported events occurred on approach to landing. Initial analysis found that at least one TCAS resolution advisory (RA) was triggered per month due to proximity to a helicopter. In over half of these instances, the helicopter may have been above the route altitude restriction. Two-thirds of the events occurred at night. A review of commercial operations (instrument flight rules departures or arrivals) at DCA between October 2021 and December 2024 indicated a total of 944,179 operations. During that time, there were 15,214 occurrences between commercial airplanes and helicopters in which there was a lateral separation distance of less than 1 nm and vertical separation of less than 400 ft. There were 85 recorded events that involved a lateral separation less than 1,500 ft and vertical separation less than 200 ft."
What is seen - reported; and what is dismissed … diminishes the value of reporting. A system broken: a broken safety management system at the national level. Subjects
DCA
FAA
NTSB
PAT25
Preliminary Report
Route Altitude
Separation (ALL)
TCAS (All)
Vertical Separation
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| Winterapfel
March 11, 2025, 20:50:00 GMT permalink Post: 11845648 |
From NTSB interim report on DCA aircraft / helicopter collision.
"Near Midair Collision Events at DCA Review of information gathered from voluntary safety reporting programs along with FAA data regarding encounters between helicopters and commercial aircraft near DCA from 2011 through 2024 indicated that a vast majority of the reported events occurred on approach to landing. Initial analysis found that at least one TCAS resolution advisory (RA) was triggered per month due to proximity to a helicopter. In over half of these instances, the helicopter may have been above the route altitude restriction. Two-thirds of the events occurred at night. A review of commercial operations (instrument flight rules departures or arrivals) at DCA between October 2021 and December 2024 indicated a total of 944,179 operations. During that time, there were 15,214 occurrences between commercial airplanes and helicopters in which there was a lateral separation distance of less than 1 nm and vertical separation of less than 400 ft. There were 85 recorded events that involved a lateral separation less than 1,500 ft and vertical separation less than 200 ft."
What is seen - reported; and what is dismissed \x85 diminishes the value of reporting. A system broken: a broken safety management system at the national level. Subjects
DCA
FAA
NTSB
Route Altitude
Separation (ALL)
TCAS (All)
Vertical Separation
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| WillowRun 6-3
March 12, 2025, 01:22:00 GMT permalink Post: 11845823 |
From NTSB interim report on DCA aircraft / helicopter collision.
"Near Midair Collision Events at DCA Review of information gathered from voluntary safety reporting programs along with FAA data regarding encounters between helicopters and commercial aircraft near DCA from 2011 through 2024 indicated that a vast majority of the reported events occurred on approach to landing. Initial analysis found that at least one TCAS resolution advisory (RA) was triggered per month due to proximity to a helicopter. In over half of these instances, the helicopter may have been above the route altitude restriction. Two-thirds of the events occurred at night. A review of commercial operations (instrument flight rules departures or arrivals) at DCA between October 2021 and December 2024 indicated a total of 944,179 operations. During that time, there were 15,214 occurrences between commercial airplanes and helicopters in which there was a lateral separation distance of less than 1 nm and vertical separation of less than 400 ft. There were 85 recorded events that involved a lateral separation less than 1,500 ft and vertical separation less than 200 ft." ...... [safetypee's emojis and comments ommitted] Almost invariably lawyers as well as law students and professors, when asked to comment about what is taught in law school, recite the truism that "law school teaches you how to think like a lawyer." Problem is, even quite modest experience in and with the realities and pressures of representing clients - i.e., practicing law - dulls the thinking part and intensifies the hustler mentalities, of which there are many variations. I'm noting this because law school actually trains you how to spot the issues. It sometimes is the case that the standard things lawyers think about a given set of issues are not the most relevant and meaningful things. With that hopefully not grossly pedantic context out of the way..... in previous comments on this thread I've noted that the federal defendants would be expected to assert sovereign immunity.... more technically, that although the Federal Tort Claims Act waives sovereign immunity in general terms, the statute also contains various exceptions - in other words, the exceptions where they apply keep sovereign immunity in place. The exception relevant here is the "discretionary function" exception, which (pardon the attempt at over-simplifying it) keeps the immunity in place if the allegedly negligent act (or omission) resulted from a federal entity's policy decision or choice. I previously viewed the discretionary function exception is likely imposing a pretty strong barrier against liability of the (probable) federal defendants. However. However. However, as I write this somewhere in an aviation law practice a mid-level or even junior associate is pounding their computer keyboard, amassing BASED ON THE ISSUES NOW REVEALED an analysis of how the discretionary function exception has never, never ever ever, been imposed to bar liability for alleged negligence roughly and/or reasonably comparable to the record of "encounters" now documented by NTSB Prelim Report. And that record goes back several years . . . but presumably discovery in United States District Court under the Federal Rules of Civil Procedure could easily reach back to even more past years. Of course, it will be said that ignoring these many encounters was indeed a policy choice, and so the exception does apply, a forum post like this notwithstanding. But that's just the point. The ISSUE here is that there never was a conscious policy directive which the alleged negligence stemmed from. Or stated another way, if I were in the aviation practice imagined above, I'd be running associates ragged to amass the above-mentioned analysis which establishes, among other things, that GROSS NEGLIGENCE by the FAA can never be, and is not as a matter of law, a predicate for applying the discretionary function exception. (For lawyers out there, somewhat akin to prima facie tort.) By the way, for all the discovery sports fans out there, just think how much fun it will be to run discovery to amass the facts of what actions - meaning by the aircraft in which the RAs were annunciated - were taken as a result of all the RAs as noted by NTSB's Prelim Report. Subjects
Accountability/Liability
DCA
FAA
NTSB
Route Altitude
Separation (ALL)
TCAS (All)
TCAS RA
Vertical Separation
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| DaveReidUK
January 27, 2026, 23:09:00 GMT permalink Post: 12028272 |
Probable Cause Statement:
The NTSB determines that the probable cause of this accident was the FAA's placement of a helicopter route in close proximity to a runway approach path.
Their failure to regularly review and evaluate helicopter routes and available data, and their failure to act on recommendations to mitigate the risk of a mid-air collision near Ronald Reagan Washington National Airport, as well as the air traffic system's overreliance on visual separation. In order to promote efficient traffic flow without consideration for the limitations of the see and avoid concept. Also causal was the lack of effective pilot applied visual separation by the helicopter crew, which resulted in a mid-air collision. Additional causal factors were were the tower team's loss of situational awareness and degraded performance due to a high workload of the combined helicopter and local control positions, and the absence of a risk assessment process to identify and mitigate real time operational risk factors, which resulted in miss prioritization of duties, inadequate traffic advisory advisories, and the lack of safety alerts to both flight crews. Also causal was the Army's failure to ensure pilots were aware of the effects of air tolerances on barometric altimeter in their helicopters, which resulted in the crew flying above the maximum published helicopter route altitude. Contributing factors include the limitations of the traffic awareness and collision alerting systems on both aircraft, which precluded effective alerting of the impending collision to the flight crew's. An unsustainable airport arrival rate, increasing traffic volume with a changing fleet mix and airline scheduling practices at DCA, which regularly strain the DCA Atct workforce and degraded safety over time. The Army's lack of a fully implemented safety management system, which should have identified and addressed hazards associated with altitude exceedances on the Washington, D.C. Helicopter routes. The FAA's failure across multiple organizations to implement previous NTSB recommendations, including Ads-b in and to follow and fully integrate its established safety management system, which should have led to several organizational and operational changes based on previously identified risk that were known to management and the absence of effective data sharing and analysis among the FAA aircraft operators and other relevant organizations. Subjects
Barometric Altimeter
DCA
FAA
NTSB
Probable Cause
Route Altitude
See and Avoid
Separation (ALL)
Situational Awareness
Visual Separation
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| Undertow
January 27, 2026, 23:41:00 GMT permalink Post: 12028291 |
Also causal was the Army's failure to ensure pilots were aware of the effects of air tolerances on barometric altimeter in their helicopters, which resulted in the crew flying above the maximum published helicopter route altitude.
Subjects
Barometric Altimeter
Blackhawk (H-60)
Route Altitude
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
Page Links: Index Page