This is an excerpt from a report made to the Aviation Safety Reporting System. The narrative is written by the pilot, rather than FAA or NTSB officials. To maintain anonymity, many details, such as aircraft model or airport, are often scrubbed from the reports.
I was the instructor during a training flight with my brother, who was acting as pilot in command (PIC) of his Aircraft X.
As we were in the traffic pattern, we were instructed by Tuscaloosa Tower to make left closed traffic for Runway 22, which we did, upon turning downwind, we were flying parallel with Aircraft Y, who had entered the traffic pattern from the south and descended into it.
Both planes were at the same spot in the traffic pattern (left downwind for Runway 22). We were flying a wider pattern than Aircraft Y.
Shortly after spotting the plane, Tuscaloosa Tower instructed Aircraft Y to make a right 360 for spacing. The pilot followed his instruction and made a right turn, which put the Aircraft Y pilot heading towards us during his turn, because of the relative position of the two planes, Aircraft Y turned behind us and finished the right 360.
Had the Aircraft Y pilot been faster or ahead of us in the traffic pattern, evasive action would have been required to avoid a mid-air collision.
This event was followed by Tower instructing us to do a right 360 for spacing also, which allowed the Aircraft Y pilot to land ahead of us.
I believe the cause of this near mid air collision was the Tower Controller’s lack of situational awareness. I do not believe he knew we were both on the downwind until he made a mistake. There were two planes in the pattern and a small plane flying a practice approach inbound, as well as a jet inbound, which I believe led to task saturation for the controller and the loss of situational awareness.
I also believe that the Aircraft Y pilot did not know where we were for the majority of this event, likely due to not being able to see us under him while he was descending into the pattern.
Primary Problem: Human Factors
ACN: 2193816
When you click on the link it will take you to the ASRS Online Database. Click on Report Number and put the ACN in the search box, then click Search. On that page, click on “view only the 1 most recent report.”
Hey fellow CFIs & PICs;
Controllers are human: If you think ATC is doing something silly that is putting you or others at risk …speak up!!!
I’m not sure I’d trundle along quiet and happy while another aircraft was intentionally turned into me, without hearing ATC point me out to them, and receive verbal acknowledgment that they had “traffic in sight”!
I don’t know if/how the other 4 reported planes factored into this goat rope; otherwise, what ATC orchestrated here makes no sense:
“Both planes were at the same spot in the traffic pattern (left downwind for Runway 22). We were flying a wider pattern than Aircraft Y.”
So…the planes were basically in a line abreast-ish formation (+/-), on downwind, with Aircraft Y closer to the runway.
I don’t care how Aircraft Y got “there” in the first place …but the two subsequent 360 degree turns were crazy-stupid, unnecessary maneuvers.
Not sure why ATC didn’t have just
the ‘outside’ aircraft, Aircraft X, do a right 360 for spacing …and roll out behind Aircraft Y.
Or…just have the ‘inside’ aircraft, Aircraft Y, fly a normal base leg …and have Aircraft X continue straight ahead on downwind for spacing?
I honestly don’t understand why pilots are filing reports with such minor drivel. It’s your job as a pilot to be aware of what’s happening around you; especially in busy controlled airspace. You, not the controller, are responsible for the safe operation of your aircraft. Controllers make mistakes. It happens every day. Work with them and carry on.
Then ask them.
As the Wise Man once said: “Trust but verify.”
Regards/J