Date: 201701
Local time of day: 1801-2400
Location: ZMA.ARTCC, FL
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Super King Air 300
Operator: Government
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Reporter organization: Government
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Communication Breakdown
Second reporter function: Pilot Flying; Captain
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented
Contributing factors: Airspace Structure; Human Factors; Procedure
Primary problem: Human Factors

Narrative: While flying a government aircraft on a government mission approximately 20 miles east of Titusville Florida as the Pilot in Command; the crew was called by a government non-FAA radar flight following center with directions to make a 180 degree turn and contact MIAMI Center.  We contacted MIAMI Center and were directed to proceed north clear of the KENNEDY SPACE CENTER FAR 91.143 SPACE OPERATIONS AREA due to an impending rocket launch from the CAPE CANAVAREL SPACE CENTER.  While diverting north clear of the airspace the aircrew queried the MIA ATC Controller about the airspace activity. The aircrew relayed to the controller that they had checked for TFR activity for Space Operations prior to flight during flight planning and did not see one; the Controller said that he would get back with the aircrew in minute.  When the Controller called back and informed the aircrew he didn't see the NOTAM either and then gave the aircrew a frequency change.  The next controller continued flight following services and gave the aircrew a number to call after landing.  During the flight we were also monitoring 121.5 on the secondary vhf radio on which we did not receive a call; our first indication of an issue was with our non-FAA government radar flight following center. After landing we contacted MIAMI CENTER at the number provided to discuss the airspace issue.  During the preflight phase the there was no Notam/TFR depicted on the flight planning system the aircrew used.  There were other TFR's depicted; but this one was not.  After landing we researched the historical Notam's for MLB and could not find a Notam for this rocket launch.  The Sectional for this area (Jacksonville) indicates the airspace is active indicated by Notam for Melbourne (MLB).  In the past the TFR has always shown up the flight planning systems used; but this evening it did not.  We received a list of Notams from MIAMI CENTER that listed a NOTAM for KZMA A0040/17 that stipulated MIAMI Center will not approve IFR Flights and VFR flights should exercise extreme caution within the area defined (which is the Space Center Airspace).  We as an aircrew always use due diligence when operating in this area; since we operate in it routinely (almost daily).  The main goal of this report is to figure out how on this one occasion we ended up in the Space Flight Area during an active period; when we checked for the specific Airspace activity as we always have done.  Flight time used in the Flying Time section of this form is approximate.


Second narrative: [Report narrative contained no additional information.]


Synopsis: A King Air 300 flight crew reported nearly flying into an active missile launch zone. The crew commented that there were no NOTAMs or other common alerts informing crews before takeoff. ATC was able to keep the flight clear of the airspace.