Small Aircraft; High Wing; 1 Eng; Fixed Gear
Air Traffic Control Time Certified In Pos 1 (yrs) 2.4
Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic; Flight Crew Requested ATC Assistance / Clarification
Airspace Structure; Airport; Human Factors; Procedure
Front Line Manager approves a Aircraft X to land (opposite direction) to the runway. Aircraft X is about 10 minutes out at this time and traffic is VERY light. No projected inbound conflictions to the opposite direction runway.  Aircraft X checks-in on about a 15 mile dog-leg final from the southwest to land opposite direction. I point-out the opposite direction aircraft to the applicable Local Controller (handling departures) and inform the Front Line Manager that Aircraft X is about 15 miles out (to ensure approach lighting is established for the runways). I initially inform Aircraft X to continue on the approach as I perform this needed coordination. I then reach back out to Aircraft X but am unable to reach the aircraft on frequency. I check the primary frequencies; secondary frequencies; check to see if he switched to the other local control; attempt to raise via 121.5 and inform the Front Line Manager of the situation. The Front Line Manager  calls down to approach to see if Aircraft X switched back to their frequency. As I am obtaining the light gun and attempting to isolate Aircraft X in the sky in order to address the correct aircraft with a green light a new aircraft calls me.  The new aircraft is Aircraft Y on what initially appeared to be a 8 mile dog-leg final to the opposite parallel runway. I cleared Aircraft Y to land opposite direction parallel runway and reattempted to target Aircraft X with the light gun; now prominently in sight about 4 mile final. However; Aircraft Y promptly retorts that he was cleared for an approach to the opposite direction runway of Aircraft X. I immediately informed Aircraft Y of the opposite direction traffic; changed & cleared Aircraft Y to land on the opposite direction parallel runway. Two small aircraft are commonly approved to land opposite direction just after sunfall as they approach the field from the West. I have observed somewhat similar situations occur in the past due to this custom approval for such a small aircraft. At times it is a conflicting departure that needs an amended heading. Sometimes it is a conflicting helicopter talking to a secondary; uninformed; local controller in the tower. Sometimes it is an event similar to the one listed above.  Not sure if communication is dropping between different arrival sectors or if the small size of the aircraft lends itself to expedited expulsion from memory. The risk vs. reward of this operation does not appear to beneficial...even when solely viewed from a perspective of airport efficiency.
I was working ground control. I am filing this because I doubt anyone else at my facility would. Aircraft X was vectored to visual approach and Aircraft Y  was vectored for a visual approach to the opposite direction runway at the same time. The Local Controller caught it and changed runways for one arrival to the parallel.I think it was just a snafu by the approach controller. This is a standard thing with this company at this time of night for his convenience.
Parallel runways were in use at the reporters airport. ATC cleared an aircraft for an opposite direction approach to the left parallel runway. The Local controller thought traffic inbound on approach was for the opposite parallel runway. The aircraft checked on Tower frequency inbound to the same opposite direction runway as the other inbound. The local controller switched the aircraft to parallel runway in a timely manner.