Page Links: First Previous 1 2 Last Index Page
| photonclock
February 03, 2025, 01:03:00 GMT permalink Post: 11820210 |
What I can say about Mike is: he puts his name and his face and his reputation out there in public to have open discussions about flight safety, and in the context of this totally preventable collision, it would be beneficial to all if every expert here and elsewhere on the interwebs participated in a similarly open and public debate in relation to this incident. If you disagree with him, message him and invite a public debate. I've lurked and read this forum for a long time. Decades? I can't even remember how long. Much as I enjoy reading it when a major incident occurs, it frustrates me to no end how it is filled with so many examples of institutional inertia, acquiescence to mind-numbingly antiquated regulations, ridiculous politics, and endless excuses, all of which inhibit the progress of technology and safety...not to segue into a rant but the most obvious example being, and which 99% of the non-flying public would agree with, that there is almost zero reason at this point to not have cameras in the cockpit and perhaps even live transmission of video and/or audio feeds on every commercial aircraft at this point \x96 the power and data/bandwidth requirements being miniscule relative to the benefits, at this point it is simply absurd that such features do not exist; the Jeju incident's loss of CVR data being the best recent example of what a hindrance to technological progress aviation regulations have become, when for a few dollars a consumer can own a tiny little dashcam that records stunning 4K video and broadcast quality audio in near total darkness with 100mph wind noise running on a small and safe lithium batteries trickle charged from a 5 watt power supply for days on end, which can be broadcast via wifi link to Starlink-satellite based internet across the entire planet. We live in the Space Age, but the data storage and recovery procedures for commercial aircraft still hearkens back to WW2... That rant aside, as the videos posted above by others demonstrate: - A Blackhawk can in fact stop on a dime (so whatever you're suggesting Mike Blackstone was wrong about, it certainly wasn't that). - Obviously that shouldn't be the plan , but it still a legitimate question to ask, in the context of an emergency, and when every other safety precaution has already failed, why couldn't it be done? Other poster's rationalize: at the low altitude, there's nowhere to go. The videos demonstrate otherwise. You can stop a Blackhawk 50 feet above the ground in seconds. If deviating in any direction is a risk, why didn't ATC just say " PAT25 slow to stop and hover!" \x96 as a Very. Last. Resort? - I don't understand how we can have a system of "Air Traffic Control" that defers its control to aircraft at night around a busy airport with intersecting approaches. It's nonsensical. I honestly didn't know it was a thing. I thought all major airports had flight paths that kept inbound and outbound aircraft in separate non-conflicting lanes at all times. Obviously, I'm extremely naive. From my perspective, it seems as though the professionals involved are allowed no intuition to deviate when the procedures clearly compromise safety? Apparently they're all reduced to being bots who can only read checklists? If that's the case, then why not run the whole system on "AI"? I know I'm being spicy by saying that, given all the pilots on this forum who harp on about how stupid AI is (true for the moment, but not for much longer, rest assured), yet many consider it perfectly reasonable for ATC procedures being to read out the type of aircraft to a pilot who is flying in total darkness in order to fulfill delegation of its responsibility to control air traffic, as if that procedure actually helps? Are we through the looking glass? It doesn't take a three year NTSB investigation to infer how stupid that is. Yet some defend it. Why? Subjects
ATC
Blackhawk (H-60)
Hover
NTSB
PAT25
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| Senior Pilot
February 03, 2025, 01:54:00 GMT permalink Post: 11820223 |
That rant aside, as the videos posted above by others demonstrate:
- A Blackhawk can in fact stop on a dime (so whatever you're suggesting Mike Blackstone was wrong about, it certainly wasn't that). - Obviously that shouldn't be the plan , but it still a legitimate question to ask, in the context of an emergency, and when every other safety precaution has already failed, why couldn't it be done? Other poster's rationalize: at the low altitude, there's nowhere to go. The videos demonstrate otherwise. You can stop a Blackhawk 50 feet above the ground in seconds. If deviating in any direction is a risk, why didn't ATC just say " PAT25 slow to stop and hover!" – as a Very. Last. Resort? My experience? 15,000 hours rotary with at least 4-5,000 hours below 200', 1,500 night hours, Mil/Civil mix of mediums (21,000lb) down to horrid little clockwork toys. No further online discussion from me, but it would be interesting to know your pilot qualifications to post here with such assumed authority, please? Subjects
ATC
Blackhawk (H-60)
Hover
Night Vision Goggles (NVG)
PAT25
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| meleagertoo
February 05, 2025, 10:32:00 GMT permalink Post: 11822080 |
Proper aviation safety is based on having multiple layers, in this case it was reduced to one (the helicopter pilot maintaining visual separation), which clearly failed. At least there should be active vectoring by ATC AND (visual acknowledgment of BOTH cockpits OR at least 500 ft vertical OR 1.5nm of horizontal separation). And even this is pushing it.
Additionally, any helicopters flying in such congested airspace should have a display showing other traffic so they know where to look outside. You cannot actively vector a helo at 200ft over the black hole of a river in the middle of an urban environment or anywhere else. You'd kill helos every month doing that. If the helo were at 100ft or so there would be no need for vectors (you never get them in London, just holding, ie orbits if necessary). Visual acknowlewgement from the aeroplane is totally unnecessary as he is on finals to land which give total priority over all other traffic. It is up to the give-way traffic to identify and acknowlege. 500ft vertical I agree with, in which case 1,5 miles is totally unnecessary and ridiculously excessive. This discussion is being considerably bogged down by a really surprising (to me) absence of understanding of helos and helo ops by people who clearly only fly f/w IFR and seem to have no concept of how the rest of the aviation world works. Strangely, there are other ways of aviating safely without staring exclusively at an instrument panel, following a magenta line and doing only what someone miles away in an office tells you. You simply cannot try to apply IFR airline type procedures and mindset to low level VFR traffic. It's like a train driver trying to dictate railway rules to a motorcyclist and being unaware that motorcycles just don't operate like trains... imaginingthat helos can or would come to a free air hover for separation is another example of unrealistic imagnation over reality. Please, if you don't know anything about helicopter ops, please don't try to apply procedural IFR or Hollywood mindsets/misapprehensions to them as if there is no other waay of flying. Last edited by meleagertoo; 5th February 2025 at 10:54 . Subjects
ATC
CRJ
Hover
IFR
Separation (ALL)
VFR
Visual Separation
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| JohnDixson
February 06, 2025, 13:35:00 GMT permalink Post: 11822990 |
fdr, bdcooper et al. The L model ( and original A models), come standard with dual SAS and airspeed hold/attitude hold and heading hold. No separate buttons for airspeed hold etc-its built into the AFCS.
Now the M model is equipped with additional features so you can if wanted have a hands off approach to a hover ( any hover height ) at any preselected destination of your choice etc. M model came after I retired so I\x92m not expert on that operation. The L model in this accident has the 3400shp gearbox and bigger engines, thus with say full tanks and three crew, and as I recall we increased the tail rotor authority. In any case, coming to a hover OGE or any other maneuver you had in mind doesn\x92t present any problems. HOGE/backwards 45 kts-whatever-have at it. Only other thing that may deserve a note is that I do believe ( subject to correction from current Hawk pilots) that they would be using NVGs which flip up so they may have them on, but can choose whether to use them. Subjects
Hover
Night Vision Goggles (NVG)
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| Lonewolf_50
August 01, 2025, 17:05:00 GMT permalink Post: 11931943 |
Do you understand what translational lift is? If they were flying at 100 kts (which is roughly what speed they seem to have been going) their static ports will work fine. Subjects
Hover
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |
| ST Dog
August 01, 2025, 19:15:00 GMT permalink Post: 11932011 |
They weren't in a hover. And backwash, when in forward flight at 100 kts? Where are you coming up with this?
Do you understand what translational lift is? If they were flying at 100 kts (which is roughly what speed they seem to have been going) their static ports will work fine. Subjects
Hover
NTSB
Reply to this quoting this original post. You need to be logged in. Not available on closed threads. |