And apparently one of those rare and vital skills is filling in the gaps when talking to air traffic controllers who are not competent to communicate life-or-death information.
This is basic preflight planning. The pilot didn't adequately prepare, given the complexity of the airspace they were flying in.
ATC isn't there to micromanage your flight. They don't need to tell you to avoid restricted airspace, it's implied.
Could he have guessed that the Anacostia would have been a better decision since the mall is just up the Potomac? Sure, maybe, but the real answer is be rude on the radio if you have to and get that clarification.
I'm not talking about wanting to go some other direction. I'm talking about the previous departure clearance he received. Those are the "A very busy air traffic controller spit out departure instructions." followed by the "hectic voice said “we have an amendment to your departure are you ready to copy”". Those are telling him which way to go. And they don't just rattle them off and good luck. They wait for the pilot to read them back, and they check that the pilot reads them back correctly.
I bet that he was not cleared for a visual departure out of DCA. So the departure he received must have had a list of nav points. Were they left or right? What restricted airspaces were there in the vicinity he should be aware of?
You know, it is telling that those details are left out. Probably if they were spelled out it would be clearer how big a mistake the pilot did. Very conveniently they are mentioned but not described.
Why not? DCA has a charted, named visual arrival. A visual departure via pilotage is no different, and is very common for VFR flights. (Yes, they would've been given a departure clearance with a route to follow, but "follow the river" is a valid VFR clearance.)
KDVA RIVER VISUAL RWY 19 - https://www.fly.faa.gov/Information/east/zdc/dca/atcCharts/D...
> What restricted airspaces were there in the vicinity he should be aware of?
That's on the chart. ATC doesn't need to (and usually won't) tell you about those. It's expected the pilot has done adequate preflight planning to be aware of them.
Pilots are always responsible for flying their aircraft in a safe manner. At the same time, the whole system must allow for pilots to do this. It has been many years since aircraft incidents have been investigated in a monocausal manner; the whole system is examined each time.
ATC expects a high level of professionalism from pilots, especially at a major airport.
(I know nothing of the vagaries of air control)
It's also important to recognize that controllers are human and can only deal with one thing at once. The current system generally speaking gives one human control over one section of airspace.
In this specific case the pilot should have been aware of the restricted airspace and set a flight plan that took them away from it before turning to their destination. There is zero excuses for flying into restricted airspace as there are published maps. The zone around the WH and USC is a permanent zone, so even less of an excuse.
Radio works pretty well and it's flexible. Imagine some asshole is flying a drone around on short final. It's easy enough to say "Hey heads up everyone, there's a DJI buzzing around at 200'", but with a more streamlined system there might not be an easy way to communicate that, and if you have the new system and radios then you still need to commmunicate everything on both while everyone adopts the new system.
Set a calendar reminder for the afternoon of July 23, 2023 in UTC-5, and go listen to the audio channel for the north ATC sector for AirVenture arrivals at KOSH. You'll get what I mean.
Put on your systems theory hat when thinking about alternatives.
FWIW, As was discussed in the post, ground/departure channels at a major airport were overwhelmingly busy for a private pilot untrained in that environment. As an occasional private passenger, I'm accustomed to quite low radio traffic because of the routes and airports we use. I've heard radio so quiet that a Controller handed us off to... herself on a different frequency for a different airspace.
But aren't most of the comms really rote and mundane instructions that follow a standard pattern? We trust automated systems to land the plane, [1] why not to tell a plane to say, cross runway 22 and stop at threshold Z?
A human could still give that instruction, but with a button instead of their mouth parts flapping? Then the radio channel would be more open for higher urgency stuff.