Narrative:

This situation was finally resolved 35 mi from the departure airport. The C210 was proposed IFR from a non radar satellite (tower controled) airport. The tower's IFR release procedure calls for the satellite tower controller to obtain an IFR release from the control facility (TRACON). No release was obtained, and the aircraft was cleared for takeoff, flying the IFR departure procedure. The C210's first call was to the departure controller (me), advising that he was 'off falcon.' when I queried the pilot for his request, he stated he was 'nwbound,' for the V105 airway to prescott. I advised the aircraft to contact the next (adjacent) sector and remain below class B airspace. The adjacent sector controller discovered the aircraft was IFR, and subsequently went 'on his way' IFR. The burden of responsibility rests on the satellite local controller, but there are additional ingredients that contributed to this event. 1) the pilot's initial call to departure control was incomplete, incorrect, and unprofessional: 'off (xyz airport)' is a poor example. 2) the pilot's transponder was set on the wrong beacon code from what had been assigned in the clearance -- the radar data did not acquire, and 3) an aircraft on an IFR clearance -- when an instrument flight is told to remain outside class B airspace, the pilot needs to question the controller.

Related reports:

Google
 

Original NASA ASRS Text

Title: ATCT LCL CTLR CLRED A C210 ON AN IFR FLT PLAN FOR TKOF WITHOUT OBTAINING AN IFR DEP RELEASE FROM PHX TRACON DC.

Narrative: THIS SIT WAS FINALLY RESOLVED 35 MI FROM THE DEP ARPT. THE C210 WAS PROPOSED IFR FROM A NON RADAR SATELLITE (TWR CTLED) ARPT. THE TWR'S IFR RELEASE PROC CALLS FOR THE SATELLITE TWR CTLR TO OBTAIN AN IFR RELEASE FROM THE CTL FACILITY (TRACON). NO RELEASE WAS OBTAINED, AND THE ACFT WAS CLRED FOR TKOF, FLYING THE IFR DEP PROC. THE C210'S FIRST CALL WAS TO THE DEP CTLR (ME), ADVISING THAT HE WAS 'OFF FALCON.' WHEN I QUERIED THE PLT FOR HIS REQUEST, HE STATED HE WAS 'NWBOUND,' FOR THE V105 AIRWAY TO PRESCOTT. I ADVISED THE ACFT TO CONTACT THE NEXT (ADJACENT) SECTOR AND REMAIN BELOW CLASS B AIRSPACE. THE ADJACENT SECTOR CTLR DISCOVERED THE ACFT WAS IFR, AND SUBSEQUENTLY WENT 'ON HIS WAY' IFR. THE BURDEN OF RESPONSIBILITY RESTS ON THE SATELLITE LCL CTLR, BUT THERE ARE ADDITIONAL INGREDIENTS THAT CONTRIBUTED TO THIS EVENT. 1) THE PLT'S INITIAL CALL TO DEP CTL WAS INCOMPLETE, INCORRECT, AND UNPROFESSIONAL: 'OFF (XYZ ARPT)' IS A POOR EXAMPLE. 2) THE PLT'S XPONDER WAS SET ON THE WRONG BEACON CODE FROM WHAT HAD BEEN ASSIGNED IN THE CLRNC -- THE RADAR DATA DID NOT ACQUIRE, AND 3) AN ACFT ON AN IFR CLRNC -- WHEN AN INST FLT IS TOLD TO REMAIN OUTSIDE CLASS B AIRSPACE, THE PLT NEEDS TO QUESTION THE CTLR.

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.