Narrative:

Air carrier X departed iah en route to mmcz. Merida acc refused X at FL330 until XX00Z. X was randomly vectored to meet the time restr. Air carrier Y departed MMMX en route to jfk. Was supposed to be assigned FL410 by monterey acc but checked on with ZHU at FL330. Even though X was kept in radar contact at all times, X infringed upon Y protected airspace along A-634. What really caused this error to occur was the lack of any type of boundary depicting radar coverage versus non-radar airspace on the controller's pvd. Even though Y was at the wrong altitude, the controller would have not let X proceed past the radar/non-radar boundary.

Google
 

Original NASA ASRS Text

Title: ACR X UNAUTH UNCOORD PENETRATION OF AIRSPACE.

Narrative: ACR X DEPARTED IAH ENRTE TO MMCZ. MERIDA ACC REFUSED X AT FL330 UNTIL XX00Z. X WAS RANDOMLY VECTORED TO MEET THE TIME RESTR. ACR Y DEPARTED MMMX ENRTE TO JFK. WAS SUPPOSED TO BE ASSIGNED FL410 BY MONTEREY ACC BUT CHKED ON WITH ZHU AT FL330. EVEN THOUGH X WAS KEPT IN RADAR CONTACT AT ALL TIMES, X INFRINGED UPON Y PROTECTED AIRSPACE ALONG A-634. WHAT REALLY CAUSED THIS ERROR TO OCCUR WAS THE LACK OF ANY TYPE OF BOUNDARY DEPICTING RADAR COVERAGE VERSUS NON-RADAR AIRSPACE ON THE CTLR'S PVD. EVEN THOUGH Y WAS AT THE WRONG ALT, THE CTLR WOULD HAVE NOT LET X PROCEED PAST THE RADAR/NON-RADAR BOUNDARY.

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.