D21 controller does not ensure handoff to yip tower where aircraft executes missed approach over air...

Attributes
ACN	485321
Time
Date	200009
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : yip.airport
State Reference	MI
Environment
Flight Conditions	IMC
Aircraft 1
Controlling Facilities	tracon : d21.tracon tower : yip.tower
Operator	general aviation : personal
Make Model Name	Cessna 210 Centurion / Turbo Centurion 210C, 210D
Operating Under FAR Part	Part 91
Flight Phase	descent : approach landing : missed approach
Route In Use	approach : instrument precision arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach controller : combined radar controller : departure
Qualification	controller : radar
Experience	controller radar : 15
ASRS Report	485321
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	airspace violation : entry conflict : ground less severe inflight encounter : weather non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : diverted to another airport flight crew : exited adverse environment
Consequence	faa : investigated
Supplementary
Problem Areas	Weather Airport ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure Operational Deviation Operational Error

Narrative:

Aircraft departed ozw en route to arb. Due to WX, aircraft went missed approach and was put in hold at sum. While in holding, aircraft handed off to lan approach. Lan took handoff and then handed aircraft off to pontiac sector (I was working ruxx sector). Aircraft went into a coast track, dropped from scope and reappeared on a 'C' tag. Aircraft asked to change destination to yip. I vectored aircraft to yip, cleared for approach and switched frequency to yip tower. Aircraft did not call yip tower until it went missed approach. Yip had an aircraft in position and hold waiting for departure release. Aircraft on approach was a 'C' tag with 'arb' in 'scratch pad' in the data block. Yip tower claims they did not see aircraft on their BRITE and no knowledge of who he was or what he was doing in their airspace. Due to automation problems, I was working a combined sector with numerous departures off dtw and sat arrs.

Original NASA ASRS Text

Title: D21 CTLR DOES NOT ENSURE HDOF TO YIP TWR WHERE ACFT EXECUTES MISSED APCH OVER ACFT ON RWY.

Narrative: ACFT DEPARTED OZW ENRTE TO ARB. DUE TO WX, ACFT WENT MISSED APCH AND WAS PUT IN HOLD AT SUM. WHILE IN HOLDING, ACFT HANDED OFF TO LAN APCH. LAN TOOK HDOF AND THEN HANDED ACFT OFF TO PONTIAC SECTOR (I WAS WORKING RUXX SECTOR). ACFT WENT INTO A COAST TRACK, DROPPED FROM SCOPE AND REAPPEARED ON A 'C' TAG. ACFT ASKED TO CHANGE DEST TO YIP. I VECTORED ACFT TO YIP, CLRED FOR APCH AND SWITCHED FREQ TO YIP TWR. ACFT DID NOT CALL YIP TWR UNTIL IT WENT MISSED APCH. YIP HAD AN ACFT IN POS AND HOLD WAITING FOR DEP RELEASE. ACFT ON APCH WAS A 'C' TAG WITH 'ARB' IN 'SCRATCH PAD' IN THE DATA BLOCK. YIP TWR CLAIMS THEY DID NOT SEE ACFT ON THEIR BRITE AND NO KNOWLEDGE OF WHO HE WAS OR WHAT HE WAS DOING IN THEIR AIRSPACE. DUE TO AUTOMATION PROBS, I WAS WORKING A COMBINED SECTOR WITH NUMEROUS DEPS OFF DTW AND SAT ARRS.

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.

D21 controller does not ensure handoff to yip tower where aircraft executes missed approach over aircraft on runway.