Posts about: "Normalization of Deviance" [Posts: 63 Page: 1 of 4]ΒΆ

Iron Duck
January 30, 2025, 15:12:00 GMT
permalink
Post: 11817315
Looking at the leaked radar plot a CA was flashing for both aircraft for approximately 20 seconds, then stopped for around 10 seconds, then started again up to the point of impact.

I suppose this is what you'll get if you routinely direct aircraft onto a collision course with each other, and therefore ignoring the CA will also become routine because you expect the pilots to sort it out. At 300' while lining up on short final, or looking into an environment full of lights. Normalisation of Deviation.

Subjects Normalization of Deviance  Radar

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

8 recorded likes for this post.

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

procede
January 30, 2025, 15:21:00 GMT
permalink
Post: 11817322
Originally Posted by Iron Duck
Looking at the leaked radar plot a CA was flashing for both aircraft for approximately 20 seconds, then stopped for around 10 seconds, then started again up to the point of impact.

I suppose this is what you'll get if you routinely direct aircraft onto a collision course with each other, and therefore ignoring the CA will also become routine because you expect the pilots to sort it out. At 300' while lining up on short final, or looking into an environment full of lights. Normalisation of Deviation.
What surprised me more is that another aircraft to the south was also showing RA for no apparent reason. It seems this system is giving so many 'false' warnings so that it is essentially ignored...

Subjects Normalization of Deviance  Radar

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.

fdr
January 30, 2025, 17:54:00 GMT
permalink
Post: 11817466
Originally Posted by thparkth
Imagine being that ATC right now. As if yesterday wasn't horrific enough, the President of the USA is now on TV implying that the accident was directly your fault, and that you are a mentally-handicapped diversity hire.
For a minute there, I misread your post, and thought that Trump was the mentally handicapped diversity hire!

Hanging the ATCO on duty will not bring back the dead, and was not the cause of the problem. Having a civil aircraft flight path immediately overhead a LL RW VFR transit lane that guarantees that there is a loss of separation standards is what set this off, and that has been the case for decades. The crews, pax, ATC officers and families just happened to be the ones that got caught out by the insanity that permitted this track and procedure to exist.

Will Mr T go after the ATC guy? probably, the ATC officer doesn't own a kingdom, a corporation, in fact he is highly unlikely to have a DUI, and certainly won't be a convicted felon. So, I would rate the ATC guy as the convenient fall guy for the US Govt, the FAA who should not have permitted the operation of civil aircraft proximate to military LL traffic, and the US DOD, who will have signed off on the practice of disregarding minimum separation per \xa791.111. As far as right of way, the CRJ was landing, \xa791.113(g) applies, notwithstanding 91.113(d). The CRJ had every reasonable expectation of not sharing a cockpit on short finals to a short runway with crossing helo traffic.
  • IDTEK is 1.4nm from touchdown, 490' PA
  • the east bank of the river is half way to the runway, ~0.7nm, -> 245'+40' = 285'PA
  • the collision occurred around mid river, ~0.3-0.4nm from T/D, or 125+40=165'
How does a 200' transit height down the east side of the river overwater provide any reasonable separation for the guys who were unfortunate last night to be the graphic example of normalisation of deviation, by the US GOVT, FAA, and US DOD.

What is particularly annoying is that the generals and other command staff, and Secretaries of Transport, Defence etc are quite happy to cashier the F-18 pilots who do a slow flypast of an arena, or the T-38 instructors who do the same over some other game, and yet, what is the chance that any general takes responsibility for their part in this sorry state of affairs. responsibility like other stuff, only goes downwards,

Its pretty easy for the guy in charge to defame the ATCO.

Glass houses.











Subjects ATC  ATCO  CRJ  FAA  Normalization of Deviance  President Donald Trump  Separation (ALL)  VFR

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

33 recorded likes for this post.

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

galaxy flyer
January 31, 2025, 14:55:00 GMT
permalink
Post: 11818269
Originally Posted by Alpine Flyer
If it was circling they‘d be expected to join the missed approach of the approach they executed.

In real life they‘d most likely get vectored.
Actually, IF the plane was cleared for an approach that’s true, however IF on visual as the CRJ was, you cannot rejoin the IAP missed approach because you weren’t cleared for an IAP. At DCA, they use visual to 33 is used because airlines do not have circling in their OpsSpecs, so it’s a visual to 33. DC, like Teterboro and DuPage (Chicago) use this weird approach to a visual because the controller cannot protect the MAP due to airspace. Teterboro gives an ILS 6 circle to 01 but begin the circling well outside the circling airspace. DuPage will give you an approach but you have to cancel IFR to visually line up with the NW runway. Both of these “workarounds” have resulted in accidents.

JFK’s Canarsie in the old days was straight in that wasn’t to get around the rules. There’s a lot of normalization of deviance in FAAland.

As a survivor of an A-10 mid-air with similar geometry and height, it easy to imagine the event.

Last edited by galaxy flyer; 31st January 2025 at 15:00 . Reason: Clean up a mistake

Subjects ATC  CRJ  DCA  IFR  Normalization of Deviance

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.

gretzky99
January 31, 2025, 15:55:00 GMT
permalink
Post: 11818314
Originally Posted by NIBEX2A
Interestingly, if the SMS works in the US the same as everywhere else in the world, procedures should be audited on a regular basis, with a focus on any changes which may have invalidated the original assumptions made about the frequency of hazards and associated risks. These procedure reviews would also take place after receipt of any safety reports where the procedure could have been a contributing factor.

The NASA ASRS database contains safety reports raised over the US. A quick search with the term \x93helicopter\x94 produced 40+ reports with the highlights shown below.. (apologies, to save time these are all copy and pasted) There are more, but I appreciate that most of us have annual eye examinations to pass so didn\x92t want to overdo it!

^^^^^^^^
Wow. That\x92s a pretty damming list of incident reports right there. Seem like a textbook example of Normalisation of Deviance.

Subjects Normalization of Deviance

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.

cyrano_de_bergerac
January 31, 2025, 22:33:00 GMT
permalink
Post: 11818580
Originally Posted by MickG0105
To provide some context,
  • more than half (26) of the 48 reported incidents occurred in the 1990s.
  • there were ten incidents reported between 2000 and 2014, inclusive.
  • there were nine incidents reported between 2015 and 2020 inclusive.
  • there were three incidents reported from 2021 to present; two incidents in 2022, and one in 2024.

The submission dates for the 16 incidents referenced in your post are as follows:
1. April 2024
2. January 2022
3. July 2018
4. July 2015
5. May 2015
6. March 2015
7. June 2013
8. May 2013
9. April 1999
10. February 1997
11. September 1993
12. August 1993
13. July 1993
14. June 1993
15. August 1992
16. April 1991
Interpretation of this statistical summary may vary widely depending on the point being argued. It is only a breakdown of one pprune'rs result's on a search for 'helicopter' in one database, so it is likely not a good representation of official safety incident data. There seems to be growing colloquial reports of past close calls on approach to 33, and general consensus that this was an accident waiting to happen wrt a 'normalization of deviance' in the design of the route 1 & 4 on this chart specifically, and some aspects of the US ATC safety culture generally. Thus if incident reporting of heli/aircraft conflicts have dropped that much, I would personally suspect some aspects of the reporting process (or social or systemic factors) are inhibiting the reporting.

Subjects ATC  Accident Waiting to Happen  Close Calls  Normalization of Deviance

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.

fly-by-wife
January 31, 2025, 23:15:00 GMT
permalink
Post: 11818608
C ommercial aviation demand outstripping capacity
O ver reliance on "see and avoid" in ATC
M ixture of military and civil traffic in terminal areas
P olitical interference at Federal level
L essons not learned from previous incidents
A TC shortages and chronic understaffing
C omplexity of airspace around major cities
E quipment and technology outdated or inadequate
N ormalisation of deviance
C onvenience chosen over safety
Y our luck runs out

Subjects ATC  Normalization of Deviance  See and Avoid

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

12 recorded likes for this post.

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

RatherBeFlying
February 01, 2025, 20:50:00 GMT
permalink
Post: 11819292
  1. Thanks to Henra for reminding us that the ATC radar displays altitudes to the nearest 100 \xb150'
  2. The nytimes.com images of heli positions outside the depicted corridors posted by fdr in #578 is massive evidence of normalisation of deviance
  3. I am beginning to suspect that the CAs noted by the controller are a commonplace occurrence. It would be interesting to learn the frequency of DCA CAs between the helicopters and traffic on approach and departure. How much and how long has deviance been normalized?
  4. 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.

Subjects ADSB (All)  ATC  CRJ  DCA  Normalization of Deviance  Radar

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.

artee
February 02, 2025, 01:26:00 GMT
permalink
Post: 11819432
Originally Posted by Denflnt
The CRJ was diverted to 33 because of traffic. No other reason. The pattern was congested, so ATC diverted them to relieve those issues for them at the time. The CRJ could have declined the ATC's request, but they would have had to circle for another approach to R1. From what I have seen, the CRJ adapted to that request professionally and ATC should have made sure that they were safe. Instead, ATC put the onus on the helo crew to maintain a safe airspace. That't the ATC's job, especially given the situation.

Ws should expect more.
My understanding is that the helo crew requested VFR, which ATC accepted. So essentially the helo crew requested the onus. Whether ATC should have accepted is a valid question, but it seems to have been commonplace. Normalisation of deviance?

Subjects ATC  CRJ  Normalization of Deviance  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.

YRP
February 02, 2025, 02:19:00 GMT
permalink
Post: 11819453
Originally Posted by RatherBeFlying
The nytimes.com images of heli positions outside the depicted corridors posted by fdr in #578 is massive evidence of normalisation of deviance
I wonder if controllers allow variation from the corridor when 33 is not being used. So helo pilots get used to cutting the corner?

Also that plot might include times when helo pilots get other routing due to no DCA traffic. Speculating, but some of those points are pretty close to the airport.


Last edited by YRP; 2nd February 2025 at 02:34 .

Subjects DCA  Normalization of Deviance

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

1 recorded likes for this post.

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

Denflnt
February 02, 2025, 02:53:00 GMT
permalink
Post: 11819469
Originally Posted by artee
My understanding is that the helo crew requested VFR, which ATC accepted. So essentially the helo crew requested the onus. Whether ATC should have accepted is a valid question, but it seems to have been commonplace. Normalisation of deviance?
The helo was always always flying VFR. ATC's job was protecting the CRJ.

Subjects ATC  CRJ  Normalization of Deviance  VFR

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.

The Blu Riband
February 02, 2025, 06:12:00 GMT
permalink
Post: 11819533
Originally Posted by gretzky99

It's a symptom of a system operating beyond its capacity.

The fact that this sort of procedure is so normalised that many crew don\x92t even see this as a threat is quite telling about the safety culture within the US aviation sector. Someone above mentioned that night circling approaches are not approved in many company Ops Manuals, so ATC issue late visual approaches instead, as a means to work around this limitation. This should be ringing alarm bells to all.

This sort of thing wouldn\x92t even be attempted in most parts of the world, let alone allowed to become normal sop.
Exactly.
Plus the often aggressive and intimidating tone from US ATC, and their habit of simply talking faster and saying everything multiple times (eg say again), has persuaded pilots and controllers that they are "making it work"
Whereas it's a classic example of Normalisation of Deviance

Subjects ATC  Normalization of Deviance

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

1 recorded likes for this post.

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

ATC Watcher
February 02, 2025, 09:27:00 GMT
permalink
Post: 11819621
Originally Posted by galaxy flyer
. Apply EASA aviation standards and the US network would grind to halt or create huge gaps in service......... Our economy would suffer greatly and passengers revolt at what would required.
.
and from island air photo :
And yes, trying to do EU IFR for everything all the time would create some epic traffic jams
Spot on, but there is no EU or EASA IFR there are IFR rules and agreed global aviation standards ,Period What is ( or should I say was ) done in DC , or in SFO or with LAHSO, etc are all deviations to allow more traffic outside of the rules. Expedition taking over our good old "safety first" mantra .

Now , is delegating visual separation to an Helicopter ,at night ,( with pilots wearing NGV ) on an aircraft cleared off the ILS doing a circle visual NPA at 500 ft with 4 eyes most probably locked on the PAPI something safe ? with a 150- Ft margin of error designed on the chart ? But it is how the system was built and local controllers trained on doing this , since years. Normalization of Deviance.

I wish good luck to the NTSB and the FAA is trying to reverse this .

Subjects FAA  IFR  Land and Hold Short  NTSB  Normalization of Deviance  Separation (ALL)  Visual Separation

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

9 recorded likes for this post.

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

island_airphoto
February 02, 2025, 13:57:00 GMT
permalink
Post: 11819813
Originally Posted by ATC Watcher
and from island air photo :

Spot on, but there is no EU or EASA IFR there are IFR rules and agreed global aviation standards ,Period What is ( or should I say was ) done in DC , or in SFO or with LAHSO, etc are all deviations to allow more traffic outside of the rules. Expedition taking over our good old "safety first" mantra .

Now , is delegating visual separation to an Helicopter ,at night ,( with pilots wearing NGV ) on an aircraft cleared off the ILS doing a circle visual NPA at 500 ft with 4 eyes most probably locked on the PAPI something safe ? with a 150- Ft margin of error designed on the chart ? But it is how the system was built and local controllers trained on doing this , since years. Normalization of Deviance.

I wish good luck to the NTSB and the FAA is trying to reverse this .
This is conflating two issues:
1.The bat-s### crazy way they run helicopters around DCA.
2. The usual practice of visual approaches and spacing in good weather. It has been that way for as long as I have been flying and I am having a hard time even visualizing all IFR spacing to the pavement on a clear day. Maybe asking an American about this is like asking a fish if water is wet?

The OTHER unrelated (?) issue of sorting out ground traffic. I was one on the same trip cleared to take off with an aircraft on short final and then cleared to land with an airplane just pulling out onto the active. To make that one better, I knew the person flying that plane and couldn't resist being snarky: "Ah XYZ tower, we'll be going around, Bob says not to wreck his airplane by landing on it".

Subjects ATC  DCA  FAA  IFR  Land and Hold Short  NTSB  Normalization of Deviance  Separation (ALL)  Visual Separation

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.

vegassun
February 03, 2025, 01:06:00 GMT
permalink
Post: 11820211
Originally Posted by ATC Watcher
and from island air photo :

Spot on, but there is no EU or EASA IFR there are IFR rules and agreed global aviation standards ,Period What is ( or should I say was ) done in DC , or in SFO or with LAHSO, etc are all deviations to allow more traffic outside of the rules. Expedition taking over our good old "safety first" mantra .

Now , is delegating visual separation to an Helicopter ,at night ,( with pilots wearing NGV ) on an aircraft cleared off the ILS doing a circle visual NPA at 500 ft with 4 eyes most probably locked on the PAPI something safe ? with a 150- Ft margin of error designed on the chart ? But it is how the system was built and local controllers trained on doing this , since years. Normalization of Deviance.

I wish good luck to the NTSB and the FAA is trying to reverse this .
"I wish you good fortune in the wars to come"

The \x93single point of failure\x94 thing has been around forever. Reminds me of when ATC decided it was OK to start using land and hold short procedures at major air carrier airports. My airline immediately put out ALL CAPS memo that we were not to accept LAHSO clearance under any circumstances. It wasn\x92t long after that I was operating into BOS landing 27, when controller says \x93______ 123 you are cleared to land 27, ________ XYZ will be landing 22L and holding short of your runway.\x94 I politely said we can\x92t accept that clearance. Controller got PO\x92ed a bit and wanted to debate it, but in the end he removed the LAHSO clearance from the other aircraft/cancelled our landing clearance/told us to continue then subsequently cleared us to land after the other aircraft landed. The gist of all that is that ATC was miffed because everybody else was going along with their questionable tactics until I came along. In my mind it was clear: technically we would not have been accepting a land and hold short clearance, but we would all be cemetery dead if the other guy screwed up. We would be \x93dead right.\x94

Over the course of the next few weeks/months I queried every check airman/chief pilot I came across and got differing opinions from nearly every one. The majority of them leaned towards the \x93 it\x92s ok you are not landing/holding short,\x94 idea. When I would point out the \x93dead right\x94 concept they would just look at me like I was speaking Mandarin Chinese.

It seems like most pilots (myself included) have a can do attitude and are willing to help ATC out whenever they can so long as it\x92s \x93legal.\x94

There was an old captain I flew with years ago that said \x93We get paid the big bucks to say no.\x94

Subjects ATC  FAA  IFR  Land and Hold Short  NTSB  Normalization of Deviance  Separation (ALL)  Visual Separation

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

10 recorded likes for this post.

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

Someone Somewhere
February 06, 2025, 03:55:00 GMT
permalink
Post: 11822721
Nothing says 'normalisation of deviation' like 'please stop reporting near misses; we don't have time to investigate them'.

I wouldn't be surprised if the same applied to helos flying above the 200' ceiling, but that's more of an incidental factor. It would still have been unacceptably close had they been at the correct altitude, and could have been a collision if the CRJ was a little low on approach.

Subjects CRJ  Close Calls  Normalization of Deviance

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

11 recorded likes for this post.

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

Someone Somewhere
February 11, 2025, 09:56:00 GMT
permalink
Post: 11825962
This kind of smells like a "gentleman's agreement" to me, if not implied threats of retaliation.

Speculation : The helicopter crews know that if they don't report traffic in sight as soon as it's called, they'll be slowed down and deprioritised by ATC and eventually held back until they either do report the traffic, or there's a substantial gap in arrivals - see the LH A380. That makes them unpopular with their passengers and/or superiors, so they are very flexible with what 'in sight' means.

ATC likewise knows that if they push helicopter crews too hard on altitude busts, report anything involving a helicopter, or hold up either kind of traffic, they might get people breathing down their neck and certainly nothing good comes of it.

Calling traffic immediately and not enforcing separation too strictly allows both parties to 'get on with their jobs' while looking more-or-less by-the-book - until an incident like this happens.

I'm hopeful I'm wrong, but given there seems to be a long history of near misses and altitude busts this seems like the obvious conclusion. No-one high-up wanted to hear about it or change anything , because no-one had died yet.



On a slightly different note, I'm curious whether anyone is familiar with the Hierarchy of Controls by NIOSH? It doesn't map 1:1 to aviation, but it codifies some things that are 'obvious' in hindsight:


Broadly speaking, some controls are more effective than others. Wherever possible, you should attempt to use more effective controls in place of less effective ones. More effective means not just that it reduces the risk the most, but also the most reliable over time and most resistant to having rules bent, being left broken, being ignored due to alarm fatigue, or 'normalisation of deviation'. Procedures that assume everything is working perfectly and everyone is 100% competent will fail; see MCAS and a great number of other accidents.

Elimination is rarely possible but substitution (radar vs visual) and isolation (separate helicopters from other traffic) amongst other engineering controls are potentially more feasible, and much higher up the hierarchy than a glorified instruction not to crash (the very bottom of administrative). Engineering a problem out of existence is far superior to having a procedure to fix it in the QRH.

I list things like TCAS, GPWS, RSAs, and crash-proof seating as broadly being under PPE: they're nice to have and certainly worth pursuing, but unless there is no other alternative, they should never be your primary protection. Something has gone wrong if they get used.


Subjects ATC  Close Calls  Normalization of Deviance  Radar  Separation (ALL)  TCAS (All)  Traffic in Sight

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.

ATC Watcher
February 12, 2025, 16:42:00 GMT
permalink
Post: 11826805
Originally Posted by bill fly
Hi, ATC Watcher,
I am sorry you see a witch hunt in my post. It was supposed to be an idea for a future improvement, rather than a criticism of the very hard worked man who was on the job. On the flying end, there is quite a rigid procedure to follow if a TCAS RA goes off. From posts since I see, that there seems to be one for for STCA triggers too. It seems to me that the gravity of the situation is brought faster to a pilot's attention if the Conflict warning is announced on the RT.
That is just one factor in this sad affair of course. Both TCAS and STCA are last ditch saviours but only if full attention can be paid to them.
Hi Bill , understood, I was a bit too harsh maybe, but I get upset to continuously read what the controller should have done. Remember he was trained like this , to follow procedures that were basically unsafe in order to move the traffic . I can say unsafe because they were removed immediately after the accident , not waiting for the NTSB to recommend it . No everyone is stupid in the FAA , they knew this route was in conflict with 33 Visual arrivals. And did not pass any safety case, but the procedure was kept , most probably due political or military pressures , relying on controllers and pilots to mitigate the risks.

Now on the Conflict alert on the BRITE display . I have no first hand info on the SOPs in DCA on how a TWR controller uses the BRITE and if STCA are even displayed . `, but if they are, seen the charts and the routes , I guess STCA alerts are very common .especially when you delegate separation and you then play with a couple of hundred feet, vertical separation Too many unnecessary alerts equals normalization of deviance, . Look at the Haneda preliminary report , same ..

Finally since you mention TCAS RAs , there is a major difference with STCA , it is not the same as a TCAS RA . With an RA , as a pilot you have to react and follow , it is mandatory , for a controller a STCA is just an alert , just like a TCAS TA , if in your judgement it will pass you will not do anything , and if you have already issued a correcting instruction ( heading, level , etc,,) or here delegate visual separation , the STCA just becomes a nuisance. .

I sincerely hope the DC Controller will not be made the scapegoat of this accident . Not so sure it will not.

Subjects ATC  DCA  FAA  NTSB  Normalization of Deviance  Preliminary Report  Separation (ALL)  TCAS (All)  TCAS RA  Vertical Separation  Visual Separation

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

9 recorded likes for this post.

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

PJ2
February 12, 2025, 19:46:00 GMT
permalink
Post: 11826918
Originally Posted by ATC Watcher
Hi Bill , understood, I was a bit too harsh maybe, but I get upset to continuously read what the controller should have done. Remember he was trained like this , to follow procedures that were basically unsafe in order to move the traffic . I can say unsafe because they were removed immediately after the accident , not waiting for the NTSB to recommend it . No everyone is stupid in the FAA , they knew this route was in conflict with 33 Visual arrivals. And did not pass any safety case, but the procedure was kept , most probably due political or military pressures , relying on controllers and pilots to mitigate the risks.

Now on the Conflict alert on the BRITE display . I have no first hand info on the SOPs in DCA on how a TWR controller uses the BRITE and if STCA are even displayed . `, but if they are, seen the charts and the routes , I guess STCA alerts are very common .especially when you delegate separation and you then play with a couple of hundred feet, vertical separation Too many unnecessary alerts equals normalization of deviance, . Look at the Haneda preliminary report , same ..

Finally since you mention TCAS RAs , there is a major difference with STCA , it is not the same as a TCAS RA . With an RA , as a pilot you have to react and follow , it is mandatory , for a controller a STCA is just an alert , just like a TCAS TA , if in your judgement it will pass you will not do anything , and if you have already issued a correcting instruction ( heading, level , etc,,) or here delegate visual separation , the STCA just becomes a nuisance. .

I sincerely hope the DC Controller will not be made the scapegoat of this accident . Not so sure it will not.
Concur. Scapegoating stochastically guarantees a repeat incident/accident of the same kind under "rhyming" circumstances.

Rarely does the "bad apple" theory of accident causation survive the scrutiny of a robust, honest investigation.

Last edited by Senior Pilot; 12th February 2025 at 23:14 . Reason: Quote was unreadable

Subjects ATC  DCA  FAA  NTSB  Normalization of Deviance  Preliminary Report  Separation (ALL)  TCAS (All)  TCAS RA  Vertical Separation  Visual Separation

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

9 recorded likes for this post.

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

HaroldC
February 16, 2025, 04:57:00 GMT
permalink
Post: 11828979
Originally Posted by ATC Watcher
Hi Bill , understood, I was a bit too harsh maybe, but I get upset to continuously read what the controller should have done. Remember he was trained like this , to follow procedures that were basically unsafe in order to move the traffic . I can say unsafe because they were removed immediately after the accident , not waiting for the NTSB to recommend it . No everyone is stupid in the FAA , they knew this route was in conflict with 33 Visual arrivals. And did not pass any safety case, but the procedure was kept , most probably due political or military pressures , relying on controllers and pilots to mitigate the risks.

Now on the Conflict alert on the BRITE display . I have no first hand info on the SOPs in DCA on how a TWR controller uses the BRITE and if STCA are even displayed . `, but if they are, seen the charts and the routes , I guess STCA alerts are very common .especially when you delegate separation and you then play with a couple of hundred feet, vertical separation Too many unnecessary alerts equals normalization of deviance, . Look at the Haneda preliminary report , same ..

Finally since you mention TCAS RAs , there is a major difference with STCA , it is not the same as a TCAS RA . With an RA , as a pilot you have to react and follow , it is mandatory , for a controller a STCA is just an alert , just like a TCAS TA , if in your judgement it will pass you will not do anything , and if you have already issued a correcting instruction ( heading, level , etc,,) or here delegate visual separation , the STCA just becomes a nuisance. .


I sincerely hope the DC Controller will not be made the scapegoat of this accident . Not so sure it will not.
I agree that the DC controllers should not be scapegoated. At the same time, the concept of professionalism must be addressed. The concept that professionals in a field must alone (without management, without lawyers, without the public) maintain the best practices of the given professional discipline.

In the US, physicians who work for "Health Maintenance Organizations" are asked to practice medicine, at times, in a "basically unsafe" manner...to keep patients moving. On occasion, such practices will bite a patient (and sometimes the physician). As a whole, HMO physicians do not enjoy the best reputation.

From my perspective, there is practically no difference between the plight of an American air traffic controller and an American HMO physician. Both are expected to "squeeze one more in." Both fields are staffed by above-average capable individuals who thrive on challenges. Both are managed in such a manner that they cannot say "no" and also keep their job. In this regard, at least physicians have job portability.

But the take home point is that one cannot admit to knowing a practice is fundamentally unsafe, yet do it anyway. The public, rightfully, should not accept this. I have no solution except more staff and/or more airports (and not some next-gen whizzbang computer system).

Subjects ATC  DCA  FAA  NTSB  Normalization of Deviance  Preliminary Report  Separation (ALL)  TCAS (All)  TCAS RA  Vertical Separation  Visual Separation

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

1 recorded likes for this post.

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