|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||navaid : oom.vortac|
|Altitude||msl single value : 5|
|Controlling Facilities||tracon : huf.tracon|
|Make Model Name||Cessna 340/340A|
|Navigation In Use||other vortac|
|Flight Phase||climbout : intermediate altitude|
|Affiliation||government : faa|
|Function||controller : departure|
|Qualification||controller : radar|
|Experience||controller radar : 6|
|Affiliation||government : faa|
|Function||controller : radar|
|Anomaly||airspace violation : entry|
non adherence : required legal separation
|Independent Detector||other controllera|
|Resolutory Action||none taken : anomaly accepted|
|Consequence||faa : investigated|
|Problem Areas||Flight Crew Human Performance|
ATC Human Performance
|Primary Problem||ATC Human Performance|
|Air Traffic Incident||Intra Facility Coordination Failure|
Bmg (bloomington, in) tower requested release on a C340 off of runway 17, sbound. I gave release to bmg, aircraft assigned on course and 3000 ft, as per LOA. Our airspace in the vicinity of bmg is only about 14 mi around, to 5000 ft. Bmg is about 40 mi from our ASR 8 site and we frequently lose radar contact with aircraft east and south of bmg. After release, aircraft first call was approximately 8 mins later. Aircraft was already out of my airspace and into next sector (ZID, nabb sector) by that time. One of various things could have happened: 1) aircraft did not depart within 3 mins of release. If so, bmg tower should have updated the time and re-requested release. 2) bmg did not xfer communications prior to the aircraft leaving their airspace and entering ours. If so, bmg tower has part of the responsibility. 3) aircraft did not check on when switched (if done in a timely fashion). If so, pilot deviation. On my part, I needed to be more aware of the time that has passed after I issue a release, and reach out to the pilot or controller for communications. In the middle of a busy session, this got overlooked, waiting for the pilot to call me.
Original NASA ASRS Text
Title: HUF CTLR EXPERIENCED OPDEV WITH ZID.
Narrative: BMG (BLOOMINGTON, IN) TWR REQUESTED RELEASE ON A C340 OFF OF RWY 17, SBOUND. I GAVE RELEASE TO BMG, ACFT ASSIGNED ON COURSE AND 3000 FT, AS PER LOA. OUR AIRSPACE IN THE VICINITY OF BMG IS ONLY ABOUT 14 MI AROUND, TO 5000 FT. BMG IS ABOUT 40 MI FROM OUR ASR 8 SITE AND WE FREQUENTLY LOSE RADAR CONTACT WITH ACFT E AND S OF BMG. AFTER RELEASE, ACFT FIRST CALL WAS APPROX 8 MINS LATER. ACFT WAS ALREADY OUT OF MY AIRSPACE AND INTO NEXT SECTOR (ZID, NABB SECTOR) BY THAT TIME. ONE OF VARIOUS THINGS COULD HAVE HAPPENED: 1) ACFT DID NOT DEPART WITHIN 3 MINS OF RELEASE. IF SO, BMG TWR SHOULD HAVE UPDATED THE TIME AND RE-REQUESTED RELEASE. 2) BMG DID NOT XFER COMS PRIOR TO THE ACFT LEAVING THEIR AIRSPACE AND ENTERING OURS. IF SO, BMG TWR HAS PART OF THE RESPONSIBILITY. 3) ACFT DID NOT CHK ON WHEN SWITCHED (IF DONE IN A TIMELY FASHION). IF SO, PLTDEV. ON MY PART, I NEEDED TO BE MORE AWARE OF THE TIME THAT HAS PASSED AFTER I ISSUE A RELEASE, AND REACH OUT TO THE PLT OR CTLR FOR COMS. IN THE MIDDLE OF A BUSY SESSION, THIS GOT OVERLOOKED, WAITING FOR THE PLT TO CALL ME.
Data retrieved from NASA's ASRS site as of July 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.