> Overwork is an issue in general, but I don't know that it was the actual issue here.
One controller working tower duties, ground movement duties, coordinating with other ATC functions off the radio, an active emergency request, and giving clearance amendments all within 2 minutes. It's insane understaffing. On top of it, there was nobody there to take over after the crash. He worked the whole cleanup for the next 30 minutes.
This is an Olympian level elite Air Traffic Controller who was setup to fail.
I've visited towers, center facilities, and have flying (and some instructing) in the San Francisco airspace for 10 years. That kind of failure is systemic way above an individual.
FOB Shipping Point (or Origin): Responsibility transfers to the buyer as soon as the goods leave the seller's premises. You book it when it leaves your loading dock.
FOB Destination: The seller retains risk and costs until the goods reach the buyer’s location.
The sale doesn't happen until the asset transfer occurs. Before that any cash you get from the sale is balanced by the liability to actually produce the good or refund the money. Or more likely you don't get any cash but can't record the bill as accounts receivable. It's not receivable until the transfer point is crossed.
Perhaps the best benchmark for the maximum potential traffic of the community at that time comes from a Slashdot post by Rob Malda (CmdrTaco) on September 14, 2001 (https://news.slashdot.org/story/01/09/13/154222/handling-the...), detailing the site's traffic following the 9/11 attacks. This load on Slashdot itself represents the full attention of the userbase and was higher than the site normally experienced:
Normal Load: 18–20 dynamic page views per second.
Peak Load: 60–70 page views per second.
Daily Volume: 3 million page views (up from a daily average of 1.4 million).
To handle this higher load, Slashdot itself had to disable dynamic content and serve static HTML to survive this load. Their database could not handle the query volume.
A typical "Slashdotting" pushed 5 to 10 Mbps of traffic. Since many sites were hosted on T1 lines (1.5 Mbps), the pipe was instantly clogged, resulting in 100% packet loss for legitimate users.
I remember when Slashdot broke because they used an Unsigned Mediumint counter for a primary key and finally overflowed it with 16 million comments over the life of the site on Nov 6, 2006.
It was a different time back then when we still measured our installed RAM in megabytes.
I've advocated for this as well but called it a lease. We agree to run this for the duration of the lease and agree to determine whether we should extend / re-sign the lease a period of time before the expiration.
Keeps from changing up too often but also gives a conscious evaluation.
One controller working tower duties, ground movement duties, coordinating with other ATC functions off the radio, an active emergency request, and giving clearance amendments all within 2 minutes. It's insane understaffing. On top of it, there was nobody there to take over after the crash. He worked the whole cleanup for the next 30 minutes.
This is an Olympian level elite Air Traffic Controller who was setup to fail.
I've visited towers, center facilities, and have flying (and some instructing) in the San Francisco airspace for 10 years. That kind of failure is systemic way above an individual.