Narrative:

The ground controller approved opposite direction operation for a GPS approach when we were landing and departing runway 22 left/right. I circled aircraft X 7 miles off of the departure end of runway 22L; as soon as the pilot reported having the runway in sight; for left traffic runway 22L. There was no incident with the procedure other than the cumbersome odo (opposite direction operation) rules designed for large IFR airports with large fast moving aircraft; not busy VFR airports with slow moving traffic. I am sure the rules were fractured as I explained to the ground controller to never accept or approve any odo operation as it simply cannot be done with the rules as they exist. Traffic at the time were six or more aircraft in the touch and go pattern on the north runway; and I had three touch and go aircraft on my runway with other departures and arrivals.TRACON should never ever call and request an odo with the current rules in place. Period. They should find some other alternative plan of action; especially when they can see the high traffic volume at ffz at the time of their request. We would have to basically shut the airport down or execute a runway change in order to be in compliance. A runway change with 9 or more planes in the pattern would introduce a lot of unnecessary risk into the system to accommodate one IFR training flight. Also more training is apparently necessary so everyone at ffz understands that odo equals unable. Simple; I get it; why can't everyone else.

Google
 

Original NASA ASRS Text

Title: FFZ Tower Controller had to delay an aircraft to accommodate an opposite direction operation. The Controller does not feel opposite direction operations should ever be approved if there is traffic in the pattern.

Narrative: The Ground Controller approved opposite direction operation for a GPS Approach when we were landing and departing RWY 22 L/R. I circled Aircraft X 7 miles off of the departure end of Runway 22L; as soon as the pilot reported having the runway in sight; for left traffic Runway 22L. There was no incident with the procedure other than the cumbersome ODO (Opposite Direction Operation) rules designed for large IFR airports with large fast moving aircraft; not busy VFR airports with slow moving traffic. I am sure the rules were fractured as I explained to the Ground Controller to never accept or approve any ODO operation as it simply cannot be done with the rules as they exist. Traffic at the time were six or more aircraft in the touch and go pattern on the north runway; and I had three Touch and Go aircraft on my runway with other departures and arrivals.TRACON should never ever call and request an ODO with the current rules in place. Period. They should find some other alternative plan of action; especially when they can see the high traffic volume at FFZ at the time of their request. We would have to basically shut the airport down or execute a runway change in order to be in compliance. A runway change with 9 or more planes in the pattern would introduce a lot of unnecessary risk into the system to accommodate one IFR training flight. Also more training is apparently necessary so everyone at FFZ understands that ODO equals UNABLE. Simple; I get it; why can't everyone else.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.