Narrative:

I took a handoff on mlt X swbnd requesting FL410. The aircraft checked on and I climbed him to FL410. Later I noticed the aircraft heading southbound into west 373, active FL290 and below. I asked mlt X his heading and he said 180 degrees. I turned the aircraft left to 080 degrees, but by the time he completed the turn he was in the area. Before mlt X got in west 371 I called seawitch for a pointout, which was eventually approved. No flight plan information was seen to this point. This incident occurred because sju approach cleared the aircraft on a routing which penetrated the warning area. Approach should have cleared the aircraft on a routing which cleared the warning area since they knew the area was active and is a common boundary.

Google
 

Original NASA ASRS Text

Title: MLT PENETRATED WARNING AREA WITHOUT PRIOR COORD.

Narrative: I TOOK A HDOF ON MLT X SWBND REQUESTING FL410. THE ACFT CHKED ON AND I CLBED HIM TO FL410. LATER I NOTICED THE ACFT HDG SBND INTO W 373, ACTIVE FL290 AND BELOW. I ASKED MLT X HIS HDG AND HE SAID 180 DEGS. I TURNED THE ACFT LEFT TO 080 DEGS, BUT BY THE TIME HE COMPLETED THE TURN HE WAS IN THE AREA. BEFORE MLT X GOT IN W 371 I CALLED SEAWITCH FOR A POINTOUT, WHICH WAS EVENTUALLY APPROVED. NO FLT PLAN INFO WAS SEEN TO THIS POINT. THIS INCIDENT OCCURRED BECAUSE SJU APCH CLRED THE ACFT ON A ROUTING WHICH PENETRATED THE WARNING AREA. APCH SHOULD HAVE CLRED THE ACFT ON A ROUTING WHICH CLRED THE WARNING AREA SINCE THEY KNEW THE AREA WAS ACTIVE AND IS A COMMON BOUNDARY.

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.