ZMA controller described an airspace incursion event when eyw controllers failed to initiate a dm me...

Narrative:

I was training on the mth radar and noticed a mode C intruder traveling approximately 280 KTS at an IFR altitude. I questioned my trainee if he had looked into the aircraft or was aware of who it is. I had my d-side call eyw approach to inquire about the beacon code. After they looked into it; eyw gave us the call sign and stated they thought he is IFR. Meanwhile; we had descending jet traffic to 10;000 ft in conflict landing mia. After we became aware that the TBM7 was IFR; we amended our descending traffic's altitude. Had we not done this; there would have been two IFR aircraft with no approved separation. In addition; eyw approach had not switched communication to us regardless of having either a track or radar contact. There have been many aircraft departing eyw approach who have not been dm'ed; which require additional steps for the center to gain track control and could end up in a beacon code change. Whoever is clearing the aircraft for release should have to manually enter a departure message.

Original NASA ASRS Text

Title: ZMA Controller described an airspace incursion event when EYW controllers failed to initiate a DM message activating the data block. The reporter indicated this oversight is a frequent occurrence.

Narrative: I was training on the MTH RADAR and noticed a Mode C intruder traveling approximately 280 KTS at an IFR altitude. I questioned my trainee if he had looked into the aircraft or was aware of who it is. I had my D-Side call EYW Approach to inquire about the beacon code. After they looked into it; EYW gave us the call sign and stated they thought he is IFR. Meanwhile; we had descending jet traffic to 10;000 FT in conflict landing MIA. After we became aware that the TBM7 was IFR; we amended our descending traffic's altitude. Had we not done this; there would have been two IFR aircraft with no approved separation. In addition; EYW Approach had not switched communication to us regardless of having either a track or RADAR contact. There have been many aircraft departing EYW Approach who have not been DM'ed; which require additional steps for the Center to gain track control and could end up in a beacon code change. Whoever is clearing the aircraft for release should have to manually enter a departure message.

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

Attributes
ACN	980065
Time
Date	201111
Local Time Of Day	1801-2400
Place
Locale Reference	ZMA.ARTCC
State Reference	FL
Aircraft 1
Make Model Name	TBM 700/TBM 850
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy

ZMA controller described an airspace incursion event when eyw controllers failed to initiate a dm message activating the data block. The reporter indicated this oversight is a frequent occurrence.