Potential conflict between aircraft on approach and other aircraft departing. IMC WX. Operational de...

Attributes
ACN	83361
Time
Date	198803
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : mtn
State Reference	MD
Altitude	agl bound lower : 0 agl bound upper : 2500
Environment
Flight Conditions	IMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : bwi tower : mtn tower : sdf
Operator	general aviation : corporate
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Flight Phase	descent : approach landing other
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	climbout : takeoff
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : instrument pilot : commercial
Experience	flight time last 90 days : 140 flight time total : 2300 flight time type : 300
ASRS Report	83361
Person 2
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	other anomaly other other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	none taken : detected after the fact none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation other

Narrative:

On IFR flight to martin state airport. While being vectored to final approach, approach controller provided a sloppy intercept angle for the localizer intercept. Required over 110 degrees of turn to capture localizer. We were then cleared for the ILS approach and advised radar service was terminated, and to contact martin tower. When tower was contacted, their response was, 'small transport X, say your intentions.' the copilot replied that we were cleared for the approach by bwi and intended to land. Meanwhile bwi had released out of martin while we were on the approach and tower cleared him for takeoff on the same runway as we were approaching. There was sufficient horizontal sep between our aircraft and the departing aircraft as to not cause a hazard to either parties. Approach control failed to contact martin tower and advise them of us on the approach. Obviously, there was a communication breakdown between the ATC specialists. What if we would have been unable to contact the tower and the visibility had been a lot lower. I think all the blame for this one goes to the female approach controller at bwi.

Original NASA ASRS Text

Title: POTENTIAL CONFLICT BETWEEN ACFT ON APCH AND OTHER ACFT DEPARTING. IMC WX. OPERATIONAL DEVIATION.

Narrative: ON IFR FLT TO MARTIN STATE ARPT. WHILE BEING VECTORED TO FINAL APCH, APCH CTLR PROVIDED A SLOPPY INTERCEPT ANGLE FOR THE LOC INTERCEPT. REQUIRED OVER 110 DEGS OF TURN TO CAPTURE LOC. WE WERE THEN CLRED FOR THE ILS APCH AND ADVISED RADAR SVC WAS TERMINATED, AND TO CONTACT MARTIN TWR. WHEN TWR WAS CONTACTED, THEIR RESPONSE WAS, 'SMT X, SAY YOUR INTENTIONS.' THE COPLT REPLIED THAT WE WERE CLRED FOR THE APCH BY BWI AND INTENDED TO LAND. MEANWHILE BWI HAD RELEASED OUT OF MARTIN WHILE WE WERE ON THE APCH AND TWR CLRED HIM FOR TKOF ON THE SAME RWY AS WE WERE APCHING. THERE WAS SUFFICIENT HORIZ SEP BTWN OUR ACFT AND THE DEPARTING ACFT AS TO NOT CAUSE A HAZARD TO EITHER PARTIES. APCH CTL FAILED TO CONTACT MARTIN TWR AND ADVISE THEM OF US ON THE APCH. OBVIOUSLY, THERE WAS A COM BREAKDOWN BTWN THE ATC SPECIALISTS. WHAT IF WE WOULD HAVE BEEN UNABLE TO CONTACT THE TWR AND THE VIS HAD BEEN A LOT LOWER. I THINK ALL THE BLAME FOR THIS ONE GOES TO THE FEMALE APCH CTLR AT BWI.

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.

Potential conflict between aircraft on approach and other aircraft departing. IMC WX. Operational deviation.