Narrative:

I received a departure message on a government aircraft departing mry. His flight plan took him through warning area airspace. He checked onto my frequency. I coordination him with sector and then climbed him to his requested altitude (FL180 blocked to FL230). I coordination the altitude with the next sector. After I xferred control of the aircraft, the D position called to look for a 'heads up' we received on the flight plan. I then called my supervisor to ask if he had permission to go through the airspace. I then called the sector that was working the aircraft to let them know. I believe who caused the problem was the mos/stmc. My understanding is that the office who schedules the warning airspace is the same who approved the flight plan.

Related reports:

Google
 

Original NASA ASRS Text

Title: ARTCC DEVELOPMENTAL RADAR CTLR COORD, THEN XFERS A P3 TO ANOTHER CTL SECTOR WORKING AN OFFSHORE WARNING AREA. CTLR BELIEVES A DEV HAS OCCURRED AND BLAMES A FACILITY SPECIALIST RESPONSIBLE FOR MIL WARNING AREA USE COORD.

Narrative: I RECEIVED A DEP MESSAGE ON A GOV ACFT DEPARTING MRY. HIS FLT PLAN TOOK HIM THROUGH WARNING AREA AIRSPACE. HE CHKED ONTO MY FREQ. I COORD HIM WITH SECTOR AND THEN CLBED HIM TO HIS REQUESTED ALT (FL180 BLOCKED TO FL230). I COORD THE ALT WITH THE NEXT SECTOR. AFTER I XFERRED CTL OF THE ACFT, THE D POS CALLED TO LOOK FOR A 'HEADS UP' WE RECEIVED ON THE FLT PLAN. I THEN CALLED MY SUPVR TO ASK IF HE HAD PERMISSION TO GO THROUGH THE AIRSPACE. I THEN CALLED THE SECTOR THAT WAS WORKING THE ACFT TO LET THEM KNOW. I BELIEVE WHO CAUSED THE PROB WAS THE MOS/STMC. MY UNDERSTANDING IS THAT THE OFFICE WHO SCHEDULES THE WARNING AIRSPACE IS THE SAME WHO APPROVED THE FLT PLAN.

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.