Skyhawk 172/Cutlass 172
Confusion; Situational Awareness
ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Human Factors; Procedure
I was off position but in the Tower cab and I noticed an unsafe opposite direction situation occur with multiple arrivals to our crossing runway.One aircraft; [Aircraft X]; was brought in for an approach to RWY 21. At the same time; two aircraft were brought in for a RWY 03 approach [Aircraft Y and Aircraft Z]. Neither aircraft to RWY 03 were APREQ [Approval Request] with the Tower which is in violation of the locally coordinated procedures at the time. The second aircraft inbound to RWY 03; Aircraft Y; was also less than a mile away from the first aircraft [Aircraft X] to RWY 03; and did not have the first aircraft in sight. When the aircraft to RWY 21 touched down; both arrivals to RWY 03 were well inside our local cutoffs for opposite direction operations. There was no contingency plan put in place by Approach Control if the RWY 21 arrival went around.Operations to our crosswind runway should be coordinated by the Approach Control before aircraft are brought in for the approach.Opposite direction operations need to be better defined in the LOA.
Tucson Tower Controller reported an unsafe opposite direction operation resulting in an airborne conflict.