Posts by user "PPRuNeUser134364" [Posts: 7 Total up-votes: 22 Page: 1 of 1]ΒΆ

PPRuNeUser134364
January 31, 2025, 09:48:00 GMT
permalink
Post: 11818051
Originally Posted by clearedtocross
Sorry fdr, I humbly disagree. While it is near impossible to stop a light heli manually like a Robinson R22 without proper ground reference, those big junks used for all-weather rescue operations all have hover-capable autopilots. Press the button and the thing holds position even in strong winds. I am sure a Blackhawk has this feature too. And hover og at sea level is not an issue here. And I am sure you should not be allowed to fly a heli at night if you cannot perform a reasonable 360 flown shy above transition speed. Another question is if you should be allowed to fly at 200 feet at night over a built up area. But that's another story. There are so many risks staring at you with these procedures it's a wonder an accident did not happen before.
Do you have a lot of time on a 'big junk'? Randomly coming to the hover at night is not like stopping your car at a red light. And not all 'big junks' have auto-hover, particularly free-air hover capability. Even if the Blackhawk does have auto-hover, it may well have limitations and it's not always just a simple case of pressing a button. e.g. is the surface (water or land) suitable for rad alt hold? What are the rad alt height limitations? Is the auto-hover based on doppler? If so, is there a max altitude for its use? The 'big junk' I am familiar with even has a min speed on instruments (not that this was instrument conditions, but it was night which has some similar characteristics).

Despite what some people appear to be suggesting here, in my experience it's not normal just to stop a helicopter to wait for a passing aircraft to fly by.

And maybe even more importantly, why would you stop if you have no reason to suspect that the flightpath isn't clear?

Subjects Blackhawk (H-60)  Hover

Links are to this post in the relevant subject page so that this post can be seen in context.

5 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

PPRuNeUser134364
January 31, 2025, 12:24:00 GMT
permalink
Post: 11818163
Originally Posted by phantomsphorever
I fully agree with Return_2_Stand
To ask somebody if he is visual with a specific aircraft type at night is almost worthy of a Monty Python sketch.
I am old, but 20 years ago - that type of question would be more like:

- "..confirm you are visual with the aircraft at your 12'o clock - 1 Nautical Mile - same altitude - heading your way...." or
- " ..confirm you have traffic on 1 mile final Rwy 33 in sight"

So they will probably crucify the heli pilot or the controller or both.
But in reality these guys had one leg in the grave and the other one in prison, operating in this area under the procedures that were proposed and agreed by the authorities.
But that isn't the first communication that mentions the CRJ. The heli had previously been told the exact location, altitude, type and which runway the CRJ was positioning for. The heli crew replied that they were visual. It is only later that the controller refers to the CRJ in isolation (with no position) but he is simply querying 'are you still visual with the aircraft that you literally just told me you were visual with?'. There is no need for any night ID skills and even if you don't have a clue what a CRJ looks like, that entire combination of calls still make sense. I agree that if the heli had been made more aware of how proximate the CRJ was then that might have resolved an incorrect SA picture, but the heli had repeatedly told the controller that he was visual. If a procedure is designed that allows a heli to correctly pass under another aircraft by 100-200 feet, at night, is the controller really supposed to be able to judge from the tower whether they are extremely close (as would appear to be the case if they were both on the correct path) or if they were on a collision course?

Originally Posted by mikegss
[sorry, I don't know how to include nested quotes!]

SLF here. During my time working offshore in the North Sea, on a couple of occasions my return chopper to Aberdeen was "held" in the air just off the threshold to allow an incoming FW to land.
If that was a hold in the hover, it would likely have been a low hover on a cross runway (or another safe place on the airfield). I would be amazed if Aberdeen asked a heli to hold in the hover, offshore, at height, at night. Aside from the disorientation issues, it isn't a comfortable place for a heli to be in case of a malfunction. If I was coming back to Aberdeen from the North Sea and was asked to hold to the east of Aberdeen, away from the airfield, I would fly a racetrack/orbit.

Subjects ATC  CRJ  Hover  Situational Awareness

Links are to this post in the relevant subject page so that this post can be seen in context.

3 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

PPRuNeUser134364
January 31, 2025, 17:56:00 GMT
permalink
Post: 11818418
Originally Posted by D Bru
In defence of the helo crew: operating in class B (VFR, IFR no matter), who could have expected that when LC asked them to spot the CRJ and pass behind, they would be already so terribly close and closing in rapidly.....
What do you consider 'so terribly close'?

When the CRJ traffic was first called to the heli, and the heli acknowledged that they were visual, the CRJ looks to have been around 4NM south of the field.

NVGs probably aren't ideal in that environment and I haven't seen any factual statement that they were using them. Even if they were wearing them it doesn't mean they were actively using them (it is usually possible to lift them up out of the way). My only concern would be flying below 200ft, at night, across multiple bridges in an environment where there may be obstructions (not knowing the specifics of that portion of airspace). It may (or may not) have been advantageous to have one person using NVGs for ground collision avoidance, but it's a balancing act that depends on the conditions on the specific night.

Subjects CRJ  IFR  Night Vision Goggles (NVG)  Pass Behind  Pass Behind (All)  VFR

Links are to this post in the relevant subject page so that this post can be seen in context.

2 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

PPRuNeUser134364
January 31, 2025, 22:11:00 GMT
permalink
Post: 11818566
Originally Posted by D Bru
SAR Bloke Easy Street Nicd

Comments appreciated of course. Indeed, I was referring to the second LC comms with the helo (coinciding with CA alerts). Class B mandates ATC to ensure separation , no matter VFR (indeed twice requested and twice accepted) or IFR (on the question whether AA by/when accepting 33 canceled IFR or not). This IMO implies much more on ATC than re-requesting whether A/C in sight, in particular in case of CA alert, less than one good/bad minute apart.
I am not a USA airspace expert, and I'm sure there are many rules that I don't know about, but having just read the FAR AIM section on 'pilot-applied visual separation' it reads to me, as an interested foreigner, that the LC can pass responsibility for separation to a pilot if they are visual. The class B separation criteria states:

VFR aircraft must be separated from VFR/IFR aircraft/ helicopter/rotorcraft that weigh more than 19,000 pounds and turbojets by no less than:
  1. 1 \xbd miles separation, or
  2. 500 feet vertical separation, or
  3. Visual separation, as specified in paragraph  7-2-1 , Visual Separation, paragraph  7-4-2 , Vectors for Visual Approach, and paragraph 7-6-7 , Sequencing.

The rules for pilot-applied visual separation state:
  1. If the aircraft are on converging courses, inform the other aircraft of the traffic and that visual separation is being applied.
  2. Advise the pilots if the radar targets appear likely to merge.
Whilst I agree giving avoidance instructions would possibly be a sensible thing to do, I can't see that explicitly written in the FAR AIM if pilot-applied visual separation has been approved. There may be other sections (or other regulations) that go into more detail that I am not aware of.


Subjects ATC  IFR  Radar  Separation (ALL)  VFR  Vertical Separation  Visual Separation

Links are to this post in the relevant subject page so that this post can be seen in context.

No recorded likes for this post (could be before pprune supported 'likes').

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

PPRuNeUser134364
February 01, 2025, 21:00:00 GMT
permalink
Post: 11819297
Originally Posted by RatherBeFlying
  1. The CRJ crew was left out of the information loop. I have a dedicated traffic display on the top of my glider panel which shows ADS-B and Flarm traffic. A similar display would have enabled the CRJ crew to monitor traffic and get the hell out of the way when necessary.
Are you sure that they didn't have the traffic on their display?

Subjects ADSB (All)  CRJ

Links are to this post in the relevant subject page so that this post can be seen in context.

No recorded likes for this post (could be before pprune supported 'likes').

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

PPRuNeUser134364
February 02, 2025, 16:35:00 GMT
permalink
Post: 11819905
I know I'm fighting a losing battle but here goes.....

Originally Posted by DespairingTraveller
I'm struggling to make sense of the numbers being bandied about here. Apparently the NTSB has said that the CRJ was at 375 feet,

But from the beginning, various plots have shown the collision occurring in mid-river. A little work with Google Earth will show that the extended 33 centre line reaches mid-river about 3,300 feet from the aimpoint of runway 33. A 3 degree glideslope and some trig will put it at 175 feet at that range, with obvious implications. 375 feet would be a big error with not much more than half a mile left to run.

What am I doing wrong?

Also, helicopter route 4 hugs the eastern bank of the Potomac until Goose Island and doesn't cross to the western bank until Wilson Bridge. So why did the Black Hawk perform a 45 degree right turn while still abeam DCA? (See, e.g., post #25) Was it intending to route direct to Fort Belvoir, ignoring the heli routes? (I think I've seen it was operating out of Joint Base Anacostia en route to Fort Belvoir, so the fact it was still abeam DCA must have been more than obvious.)

Puzzled.
What you are doing wrong is making guesses based on incomplete/inaccurate data that is in the public domain.

Assuming the NTSB figure of 375ft is correct, you still need more info for it to mean anything. Was that the AGL, AMSL or SPS height/altitude?
How accurate are the 'various plots' that indicate the collision occurred mid-river? They may be right; they may not be.
Was the CRJ on final or was it still positioning to final? If it wasn't on final then the trigonometric calculations of what height it should be at might not be correct.
What official evidence is there that the Blackhawk made a 45 degree turn, or could that be a data error in the publicly available information?

In summary what I am saying is that, despite all of the internet sleuths plotting tracking data, none of it is official and it is all subject to various errors. Whilst interesting to form an understanding of the circumstances, it can't be assumed to be accurate to within a few feet (vertically or laterally).

Originally Posted by JohnDixson
Regarding UH-60L altimeters:
All UH-60 A and L Army aircraft incorporated the APN 209 radar altimeter. Our Sikorsky tech fellow for Avioics/electronis reports the accuracy in this area is 1-2 feet. The radar altimeter position in the instrument panel is just to the right of the attitude indicator and its top matches the top of the attitude indicator. The barometric altimeter is immediately below it.
Both pilots have the same setup.
That 1-2 feet error would be a theoretical accuracy. The readout in the cockpit would be subject to significant errors during turns/pitch changes etc; without knowing the exact installation on a Blackhawk, it might also unlock based on the surface conditions. More importantly, the ATC instructions would probably be based on an altimeter setting and not Rad Alt.

Originally Posted by uncle_maxwell
Instead of no RA below 500ft (or whatever the floor is), how about telling one conflict to climb and the other one to \x91not climb\x92? \x91Not climb\x92 could then be understood (and trained) to mean \x91descend a little, terrain/aircraft/wx permitting or fly level\x92. Lots of ifs and buts, spurious warnings, limitations for when 3 or more conflicts, TCAS vs. GPWS considerations etc. but perhaps worth a thought.
How would that have worked in this scenario? Who do you think should have been directed by TCAS to do what? Does the Blackhawk even have TCAS?



Subjects ATC  Barometric Altimeter  Blackhawk (H-60)  CRJ  DCA  NTSB  Radar  Route 4  TCAS (All)

Links are to this post in the relevant subject page so that this post can be seen in context.

6 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

PPRuNeUser134364
February 02, 2025, 18:20:00 GMT
permalink
Post: 11819978
Originally Posted by uncle_maxwell
I know it is inhibited. I am saying that the concept of TCAS can be enhanced such that RAs are possible below 500ft without instructing one of the conflicting parties to fly into terrain. It may be worth looking at for safety engineers.
Do you honestly think that you've just thought of that and the system designers haven't?

In relation to your earlier response to my previous comment, how can the system tell someone to 'remain level' when that aircraft doesn't have TCAS? I am not sure of the Blackhawk fit, but I would be pretty surprised if it has TCAS fitted.

One of the main reasons that TCAS alerts are inhibited at low altitude is to avoid distraction during the landing phase, in an area that has a high traffic density and a high probably of nuisance alerts. The system would constantly be giving RAs and people would be going around and deviating all over the place. Even if just TAs were left active then it would be going off all the time, and we would be having the same conversation about becoming blase to the warnings as we are about the repetitive conflict alerts that were being given to the LC.

Getting TCAS to give RAs on final is not the solution in my opinion.

Subjects Blackhawk (H-60)  TCAS (All)  TCAS RA

Links are to this post in the relevant subject page so that this post can be seen in context.

6 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.