Narrative:

I was working flight data/clearance delivery at dvt. Small aircraft X called me on clearance delivery for his IFR clearance to rno. I then called P50 to get his IFR clearance. I then read small aircraft X clearance to him. After completing the clearance. I then gave to the ground controller and said, 'here's an IFR.' I was instructed to combine my flight data/clearance delivery position to the ground controller position. I then pulled out the flight data/clearance delivery controller checklist. Told the ground controller all pertinent information and said, 'and of course, you're IFR,' and pointed to the IFR strip. As I was on break, small aircraft X departed without obtaining a release from P50, which resulted in an operational deviation for dvt. The ground controller knew he had an IFR and was reminded of it twice. When called ready to taxi, the ground controller treated him as if he were VFR and did not give the IFR strip to the local controller. A way to overcome this type of error would be saying to the ground controller, 'ground control, IFR strip, small aircraft X,' and then hand the IFR strip to ground control. Supplemental information from acn 246994: I was working ground control. I received a call from an aircraft who only idented himself as an small aircraft in front of the municipal building for taxi. I looked at the ramp and saw an small aircraft and could not read his call sign. Since the pilot did not give me required information, I asked him his call sign and direction of flight. He told me small aircraft X and he would be going nwbound. I instructed him to taxi to runway 25L. Since the flight progress strip was not delivered to deer valley tower in a timely manner, an since it contained incomplete and inaccurate information from phx TRACON, such as no proposed time of departure, and the strip said different type small aircraft and the aircraft was indeed an small aircraft X I was not aware that the aircraft I was talking to was IFR. This aircraft then departed without an IFR release. Phx TRACON later advised small aircraft X flew 8 mi on a VFR squawk code before calling them and the pilot relayed he wasn't sure if he was VFR or IFR. He was then given the IFR squawk code and provided service, phx TRACON then called us to advise the airplane departed without a clearance. Supplemental information from acn 246992: I was working the controller-in-charge position, monitoring the local control north and south position combined during moderate traffic. Small aircraft X called for takeoff, the pilot did not state he was IFR, the local controller was never given an IFR strip, and the plane was listed on the local controller's VFR departure board as small aircraft X northwest. So, the local controller and myself felt the aircraft was a VFR flight. After small aircraft X departed, the aircraft was squawking VFR code and never squawked his assigned IFR code while in the air traffic area. In conclusion, due to lack of information and the aircraft being listed on the VFR departure board, I was not aware that it was IFR. So then, the local controller or I did not request an IFR release from P50, resulting in the IFR departing without a release.

Related reports:

Google
 

Original NASA ASRS Text

Title: ATCT TRACON INTERFAC COORD SMA X UNAUTH UNCOORD PENETRATION OF APCH CTL AIRSPACE. OPDEV.

Narrative: I WAS WORKING FLT DATA/CLRNC DELIVERY AT DVT. SMA X CALLED ME ON CLRNC DELIVERY FOR HIS IFR CLRNC TO RNO. I THEN CALLED P50 TO GET HIS IFR CLRNC. I THEN READ SMA X CLRNC TO HIM. AFTER COMPLETING THE CLRNC. I THEN GAVE TO THE GND CTLR AND SAID, 'HERE'S AN IFR.' I WAS INSTRUCTED TO COMBINE MY FLT DATA/CLRNC DELIVERY POS TO THE GND CTLR POS. I THEN PULLED OUT THE FLT DATA/CLRNC DELIVERY CTLR CHKLIST. TOLD THE GND CTLR ALL PERTINENT INFO AND SAID, 'AND OF COURSE, YOU'RE IFR,' AND POINTED TO THE IFR STRIP. AS I WAS ON BREAK, SMA X DEPARTED WITHOUT OBTAINING A RELEASE FROM P50, WHICH RESULTED IN AN OPDEV FOR DVT. THE GND CTLR KNEW HE HAD AN IFR AND WAS REMINDED OF IT TWICE. WHEN CALLED READY TO TAXI, THE GND CTLR TREATED HIM AS IF HE WERE VFR AND DID NOT GIVE THE IFR STRIP TO THE LCL CTLR. A WAY TO OVERCOME THIS TYPE OF ERROR WOULD BE SAYING TO THE GND CTLR, 'GND CTL, IFR STRIP, SMA X,' AND THEN HAND THE IFR STRIP TO GND CTL. SUPPLEMENTAL INFO FROM ACN 246994: I WAS WORKING GND CTL. I RECEIVED A CALL FROM AN ACFT WHO ONLY IDENTED HIMSELF AS AN SMA IN FRONT OF THE MUNICIPAL BUILDING FOR TAXI. I LOOKED AT THE RAMP AND SAW AN SMA AND COULD NOT READ HIS CALL SIGN. SINCE THE PLT DID NOT GIVE ME REQUIRED INFO, I ASKED HIM HIS CALL SIGN AND DIRECTION OF FLT. HE TOLD ME SMA X AND HE WOULD BE GOING NWBOUND. I INSTRUCTED HIM TO TAXI TO RWY 25L. SINCE THE FLT PROGRESS STRIP WAS NOT DELIVERED TO DEER VALLEY TWR IN A TIMELY MANNER, AN SINCE IT CONTAINED INCOMPLETE AND INACCURATE INFO FROM PHX TRACON, SUCH AS NO PROPOSED TIME OF DEP, AND THE STRIP SAID DIFFERENT TYPE SMA AND THE ACFT WAS INDEED AN SMA X I WAS NOT AWARE THAT THE ACFT I WAS TALKING TO WAS IFR. THIS ACFT THEN DEPARTED WITHOUT AN IFR RELEASE. PHX TRACON LATER ADVISED SMA X FLEW 8 MI ON A VFR SQUAWK CODE BEFORE CALLING THEM AND THE PLT RELAYED HE WASN'T SURE IF HE WAS VFR OR IFR. HE WAS THEN GIVEN THE IFR SQUAWK CODE AND PROVIDED SVC, PHX TRACON THEN CALLED US TO ADVISE THE AIRPLANE DEPARTED WITHOUT A CLRNC. SUPPLEMENTAL INFO FROM ACN 246992: I WAS WORKING THE CTLR-IN-CHARGE POS, MONITORING THE LCL CTL N AND S POS COMBINED DURING MODERATE TFC. SMA X CALLED FOR TKOF, THE PLT DID NOT STATE HE WAS IFR, THE LCL CTLR WAS NEVER GIVEN AN IFR STRIP, AND THE PLANE WAS LISTED ON THE LCL CTLR'S VFR DEP BOARD AS SMA X NW. SO, THE LCL CTLR AND MYSELF FELT THE ACFT WAS A VFR FLT. AFTER SMA X DEPARTED, THE ACFT WAS SQUAWKING VFR CODE AND NEVER SQUAWKED HIS ASSIGNED IFR CODE WHILE IN THE ATA. IN CONCLUSION, DUE TO LACK OF INFO AND THE ACFT BEING LISTED ON THE VFR DEP BOARD, I WAS NOT AWARE THAT IT WAS IFR. SO THEN, THE LCL CTLR OR I DID NOT REQUEST AN IFR RELEASE FROM P50, RESULTING IN THE IFR DEPARTING WITHOUT A RELEASE.

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.