Page Links: Index Page
| andihce
August 10, 2025, 05:00:00 GMT permalink Post: 11936009 |
There have been a number of references above to the woefully inadequate vertical separation provided between helicopter Route 4 and the approach to Runway 33. Given altimeter errors (expected and maybe not so expected) in the helicopter, a helicopter flying high (and possibly offset sideways towards the end of Runway 33) and an aircraft maybe low on approach, there really wasn’t any guaranteed separation.
I strikes me that, from my layman’s point of view, that this is the primary and gaping hole (among numerous others) in the Swiss cheese here. At the same time, I get the sense that no controller was ever going to intentionally permit a helicopter to pass directly under an approaching aircraft and challenge that limited clearance. My question is, should this have been (or was it?) formalized as an ATC procedure? Because if this had been proceduralized, I find it hard to believe that just nighttime VFR separation would have been found acceptable in that environment. Rather I would think that lateral separation should have been actively managed by ATC. For one thing, with the CRJ (or whatever aircraft) pilots making a late switch to 33, turning to line up with the runway, etc., they may not have had the bandwidth to scan for a possibly conflicting helicopter, if they could even have seen it from their cockpit. (IIRC from the inquiry, the NTSB will be investigating that last point.) I don’t know how difficult it may have been for the helicopter to see the CRJ, but the simple fact is that they did not. On another subject, one thing that struck me from the inquiry was that the helicopter pilot apparently had very limited recent flight time, yet was assigned a challenging check ride. This contrasted with the testimony of the leader (?) of one of the local Medivac groups, who discussed how much more experience he and his pilots had flying in that challenging environment (and often single-pilot ops at that). Is the Army not providing adequate training and flight time to ensure their pilots can operate safely in those conditions? Last edited by andihce; 10th August 2025 at 06:44 . Reason: clarification Subjects
ATC
CRJ
NTSB
Route 4
Separation (ALL)
VFR
Vertical Separation
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| andihce
August 10, 2025, 07:10:00 GMT permalink Post: 11936034 |
I wouldn't bother explaining it to laymen as a hole in cheese. In layman's terms it's the same as having two busy roads cross, and no traffic lights.
And to stick with motoring analogies, some of us are used to considering that at a junction another vehicle can be partly obscured by a pillar for one eye, and in the blind spot of our other eye, so we might move our head sideways to help check better. Some aircraft have more windscreen pillars (this helicopter has four) so the aircraft in a constant relative position - which is the one that is the collision risk - may stay behind a pillar unless we move our head. The CRJ was executing a left turn for some distance up until the point of collision, while the helicopter was flying a fairly straight course. Under the actual conditions, the azimuth of the CRJ as viewed from the helicopter should have shifted significantly as the collision point was approached. Subjects
CRJ
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| andihce
August 10, 2025, 07:27:00 GMT permalink Post: 11936037 |
It's simple; the altitude restriction was never intended to be the sole method of separation. At most, it was an additional layer of protection. The controller wouldn't have cleared the Blackhawk to continue if they hadn't said they had the traffic in sight. But they did say that, whether it was true or not. ATC is a service provided to pilots, not an authority. Pilot-applied visual separation essentially overrides any procedure used by ATC. When you say "Traffic in sight," you are saying "I don't need your help maintaining separation, I have it under control and I take full responsibility."
Yet was not the controller required to inform the CRJ of the helicopter, which (as the inquiry noted) he failed to do? Thus a possible cross-check was lost. Last edited by andihce; 10th August 2025 at 07:28 . Reason: Fixed quoting Subjects
ATC
Blackhawk (H-60)
CRJ
IFR
Separation (ALL)
Traffic in Sight
Visual Separation
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| andihce
August 13, 2025, 22:32:00 GMT permalink Post: 11938086 |
Are there procedures published? If Yes, was everybody following those procedures?
If Yes, no normalisation of deviance. The procedures themselves were/are flawed, not the execution of them. If No, then there's normalisation of deviance. The users are not following the procedures and if those procedures have been in place for some time, the users have been "getting away with it" ie NoD until now. Each time someone gets away with a close call, the "normalization" sweeps the issue under the rug, instead of the procedure being questioned. The longer the procedure is in use, the more confidence there may be that it is acceptable, when in fact it may just be a matter of time until some unlikely and disastrous event occurs "by chance". Having worked in a non-aviation area that became heavily proceduralized after all too many mistakes had been made, I have seen more than a few flawed procedures that continued to be employed despite warning signs, typically because of time, management, cost, etc. pressures. Modifying and reviewing a procedure can be a time consuming process as many individuals and management structures can be involved in a complicated system. In the present case (without knowing exactly what procedures were in effect), I could argue that permitting visual separation at night in this particular environment was a key procedural flaw. But it was accepted as there had been no accidents as a result, even as perhaps traffic density, etc. increased risk over time. Last edited by andihce; 13th August 2025 at 23:53 . Reason: addition Subjects
Close Calls
Separation (ALL)
Visual Separation
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| andihce
August 16, 2025, 03:15:00 GMT permalink Post: 11939359 |
Ward Carroll posted some thoughts about the crash following the evidence a couple of weeks ago. He gives a quick summary of the faacts, and looks at the blame game.
He's quite clear that he thinks that ATC alerting the CRJ about the presence of the helo (using visual flight separation) probably wouldn't have changed the outcome. But he does pick up on the cockpit dynamics on PAT25. He says "Now, the most important facts to emerge from the hearings this week center on the cockpit exchange between Warrant Officer Eves and Captain Robach that happened just about a minute before the midair. He says to her, " All right, kind of come left for me, ma'am. I think that's why he's asking ." And she replies, " Sure ." He says, " We're kinda.. ." And she cuts him off by saying, " Oh-kay, fine ." And he finishes his statement \x93\x85 out toward the middle \x94, meaning the middle of the river and west of helicopter route 4. So PAT 25 is above and west of where they should have been as the CRJ is properly on final approach for runway 33. Using maritime rules of the road terms, the CRJ was the burden vessel and the Blackhawk was the giveway vessel." He quotes someone (David Cherbonnier) posting: Subjects
ATC
Blackhawk (H-60)
CRJ
PAT25
Route 4
Separation (ALL)
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
Page Links: Index Page