Pilot failed to file ADIZ penetration flight plan with air defense command. Operational deviation.

Attributes
ACN	129657
Time
Date	198912
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : oak
State Reference	CA
Altitude	msl bound lower : 600 msl bound upper : 600
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zoa
Operator	other
Make Model Name	Medium Large Transport
Flight Phase	cruise other
Flight Plan	VFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller non radar : 2 controller radar : 5
ASRS Report	129657
Person 2
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : published procedure
Independent Detector	other other : unspecified
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation Inter Facility Coordination Failure

Narrative:

As part of my briefing for the sector, I was told that a VFR aircraft, medium large transport X was maneuvering in the vicinity of the farallon islands, working with a ship on the water for some type of testing. The aircraft was monitoring my frequency, not under radar contact (due to low altitude, 600' AGL), and that the pilot would advise on my frequency when he was turning inbound to land at oak airport. Within the next 15-20 mins I told that the air defense command (air data computer) was launching a fgt from fresno on an active scramble to intercept an intruder off the coast. To simplify a complex story, here is what apparently occurred. 1) a VFR pilot under contract with the navy was flying over a naval ship for some sort of radar check. 2) his orbiting took him repeatedly in and out of the contiguous us ADIZ. 3) us air data computer tried to hail the aircraft on UHF/VHF 'guard' 121.5/243.0. 4) aircraft was not tuned to 'guard' because he was monitoring an ATC frequency. 5) nobody at the ARTCC was informed which was the intercept target, to circumvent the scramble. Next time maybe the navy, the FAA and the air data computer can coordinate.

Original NASA ASRS Text

Title: PLT FAILED TO FILE ADIZ PENETRATION FLT PLAN WITH AIR DEFENSE COMMAND. OPDEV.

Narrative: AS PART OF MY BRIEFING FOR THE SECTOR, I WAS TOLD THAT A VFR ACFT, MLG X WAS MANEUVERING IN THE VICINITY OF THE FARALLON ISLANDS, WORKING WITH A SHIP ON THE WATER FOR SOME TYPE OF TESTING. THE ACFT WAS MONITORING MY FREQ, NOT UNDER RADAR CONTACT (DUE TO LOW ALT, 600' AGL), AND THAT THE PLT WOULD ADVISE ON MY FREQ WHEN HE WAS TURNING INBND TO LAND AT OAK ARPT. WITHIN THE NEXT 15-20 MINS I TOLD THAT THE AIR DEFENSE COMMAND (ADC) WAS LAUNCHING A FGT FROM FRESNO ON AN ACTIVE SCRAMBLE TO INTERCEPT AN INTRUDER OFF THE COAST. TO SIMPLIFY A COMPLEX STORY, HERE IS WHAT APPARENTLY OCCURRED. 1) A VFR PLT UNDER CONTRACT WITH THE NAVY WAS FLYING OVER A NAVAL SHIP FOR SOME SORT OF RADAR CHK. 2) HIS ORBITING TOOK HIM REPEATEDLY IN AND OUT OF THE CONTIGUOUS U.S. ADIZ. 3) U.S. ADC TRIED TO HAIL THE ACFT ON UHF/VHF 'GUARD' 121.5/243.0. 4) ACFT WAS NOT TUNED TO 'GUARD' BECAUSE HE WAS MONITORING AN ATC FREQ. 5) NOBODY AT THE ARTCC WAS INFORMED WHICH WAS THE INTERCEPT TARGET, TO CIRCUMVENT THE SCRAMBLE. NEXT TIME MAYBE THE NAVY, THE FAA AND THE ADC CAN COORDINATE.

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.