Oak tower controller reports of an opposite direction arrival that gets close to his departure. The ...

Attributes
ACN	1189695
Time
Date	201407
Local Time Of Day	1201-1800
Place
Locale Reference	OAK.Airport
State Reference	CA
Environment
Light	Daylight
Aircraft 1
Make Model Name	Falcon 2000
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Final Approach
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 1.7
Events
Anomaly	Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

Narrative:

I cleared a falcon 2000 (DA2000) for takeoff and observed an opposite direction inbound jet that had been maneuvering through final and circling; turning final about 13 mile final. Both were IFR and I was not in communication with the jet on final. I switched the DA2000 to nct so they could turn them and then checked with nct to ensure they had contact with the departure; and they did. I then observed the inbound jet turning north (about perpendicular to the inbound) approximately 5 miles from the inbound traffic. There was a vip tfr in place forcing departures to depart opposite direction to avoid the tfr; and had been several arrivals that the departure had to wait for. I think the approval controller did not wait for the departure to get airborne after they gave me the IFR release and I cleared the departure. I think they were rushed and that having them tour the tower could help them to see how the flow of traffic is at the tower. The area working this departure normally does not work departures from oakland.

Original NASA ASRS Text

Title: OAK Tower Controller reports of an opposite direction arrival that gets close to his departure. The sector is one that usually does not work departures in this configuration.

Narrative: I cleared a Falcon 2000 (DA2000) for takeoff and observed an opposite direction inbound jet that had been maneuvering through final and circling; turning final about 13 mile final. Both were IFR and I was not in communication with the jet on final. I switched the DA2000 to NCT so they could turn them and then checked with NCT to ensure they had contact with the departure; and they did. I then observed the inbound jet turning north (about perpendicular to the inbound) approximately 5 miles from the inbound traffic. There was a VIP TFR in place forcing departures to depart opposite direction to avoid the TFR; and had been several arrivals that the departure had to wait for. I think the approval Controller did not wait for the departure to get airborne after they gave me the IFR release and I cleared the departure. I think they were rushed and that having them tour the tower could help them to see how the flow of traffic is at the Tower. The area working this departure normally does not work departures from Oakland.

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.

Oak tower controller reports of an opposite direction arrival that gets close to his departure. The sector is one that usually does not work departures in this configuration.