Small Transport; Low Wing; 2 Turbojet Eng
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 11
Situational Awareness; Confusion; Communication Breakdown; Time Pressure
Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Environment - Non Weather Related; Human Factors; Procedure
I put in a release for Aircraft X for Runway XXL. I called on the shout line right away to coordinate for the aircraft departing Runway XXL for winds since we were advertising Runway YYR. No other aircraft was in the airspace. The closest aircraft was outside of 20 miles and west of the airspace. Approach would not give me a release stating the aircraft was ODO [Opposite Direction Operation] with the IFR arrival. Our LOA and procedures state that this is not considered an ODO operation. The aircraft was delayed over 10 minutes for no reason. Upon the arrival landing; the Approach Controller wanted a landing verification before TRACON Controller would give me a release on the aircraft departing Runway XXL. Which is not a requirement from a Tower controlled airport. The Approach Controller also stated I needed to review LOA PROCEDURES for ODO on the shout line. This Controller unduly delayed an aircraft and was unprofessional on the shout line with me over an aircraft needing to depart a different runway. I also know that the TRACON has had a COVID schedule with several days off and then working again so I don't know if it is a proficiency issue.The Approach Controller needs to review LOA procedures with ZZZ. I would also suggest Controller visit our Tower and try to understand the Tower side of the operation. Controller caused an aircraft to waste gas and prevent expeditious movement of aircraft.
Tower Controller reported being delayed by the TRACON due to the TRACON not releasing an aircraft resulting in an airspace incursion.