An arrival aircraft conflicted with an opposite direction departure aircraft.

Attributes
ACN	113381
Time
Date	198906
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : mmu
State Reference	NJ
Altitude	agl bound lower : 0 agl bound upper : 1000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : mmu
Operator	general aviation : corporate
Make Model Name	Medium Transport
Flight Phase	climbout : intermediate altitude climbout : takeoff
Route In Use	departure other
Flight Plan	IFR
Aircraft 2
Operator	general aviation : corporate
Make Model Name	Light Transport, Low Wing, 2 Turbojet Eng
Flight Phase	descent other landing other
Route In Use	arrival other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
ASRS Report	113381
Person 2
Affiliation	government : faa
Function	controller : flight data
Qualification	controller : non radar
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Miss Distance	horizontal : 3000 vertical : 500
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Operational Error

Narrative:

Departure control had released cga Y off runway 23. Meanwhile approach asked the flight data controller if 'we could handle a runway 5 and a runway 30 right traffic'. Flight data approved the request and marked the arrival strips right traffic runway 30 and visual approach right traffic runway 5. The approach controller then said 'ok, the runway 30 right traffic and cga X straight in to runway 5.' the flight data controller replied 'roger, right traffic'. The runway 23 departure was cleared for takeoff into the face of cga X straight in to runway 5. The runway 23 departure started a 20 degree right turn as we crossed to the airport boundary, and this turn in conjunction with a good rate of climb put cga Y above and well to the right of cga X. No evasive action was necessary by either aircraft. The local controller was startled upon noticing cga X on final without her approval and filed the operational error.

Original NASA ASRS Text

Title: AN ARR ACFT CONFLICTED WITH AN OPPOSITE DIRECTION DEP ACFT.

Narrative: DEP CTL HAD RELEASED CGA Y OFF RWY 23. MEANWHILE APCH ASKED THE FLT DATA CTLR IF 'WE COULD HANDLE A RWY 5 AND A RWY 30 RIGHT TFC'. FLT DATA APPROVED THE REQUEST AND MARKED THE ARR STRIPS RIGHT TFC RWY 30 AND VISUAL APCH RIGHT TFC RWY 5. THE APCH CTLR THEN SAID 'OK, THE RWY 30 RIGHT TFC AND CGA X STRAIGHT IN TO RWY 5.' THE FLT DATA CTLR REPLIED 'ROGER, RIGHT TFC'. THE RWY 23 DEP WAS CLRED FOR TKOF INTO THE FACE OF CGA X STRAIGHT IN TO RWY 5. THE RWY 23 DEP STARTED A 20 DEG RIGHT TURN AS WE CROSSED TO THE ARPT BOUNDARY, AND THIS TURN IN CONJUNCTION WITH A GOOD RATE OF CLIMB PUT CGA Y ABOVE AND WELL TO THE RIGHT OF CGA X. NO EVASIVE ACTION WAS NECESSARY BY EITHER ACFT. THE LCL CTLR WAS STARTLED UPON NOTICING CGA X ON FINAL WITHOUT HER APPROVAL AND FILED THE OPERATIONAL ERROR.

Data retrieved from NASA's ASRS site as of August 2007 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.