Narrative:

These are 2 separate events that occurred within a few mins with mob approach. Aircraft #1 departed AL15, proceeding northwest to the M11 airport, climbing to 8000 ft. Mob approach would not take the handoff, and I had to turn the aircraft to the northeast to remain in my airspace. Aircraft #2 was wbound, descending to 6000 ft, landing bfm. Again, mob approach refused to take the handoff. When I attempted to spin the aircraft, the irate (justifiably) pilot canceled IFR. Both of the aircraft were on IFR flight plans, in the NAS system. This problem with mob approach has been ongoing for many months. We have documented numerous occasions where we have had to spin acrs, air taxies, civilian and military because they would not accept a timely handoff. Many of us have also filed ucr's, to no avail. The controllers at pns approach have complained for a long time about a problem we feel is unsafe and unnecessary. Callback conversation with reporter revealed the following information: the reporter attributes these intermittent, but constant, events to personality problems at mob approach. The 2 aircraft described in the event were on appropriate, LOA authority/authorized routings. Automation was not a factor, and aircraft were in proper handoff mode. The reporter is also concerned with other 'nonstandard operating practices' observed with certain mob approach personnel. These other 'practices' mainly focus on the early termination of VFR aircraft and the associated automated tracked flight plans. The pns controller is required to ask for pertinent information to reinitiate a tracked flight that had been already complete in the computer. Though similar sits have been occurring for almost 2 yrs, the reporter states that management has been unable to resolve these 'personality issues' with mob.

Related reports:

Google
 

Original NASA ASRS Text

Title: PNS CTLR UNABLE TO EFFECT A HDOF ON A CLBING NWBOUND BE55 AND A DSNDING WBOUND BE91 TO MOB TRACON. BOTH ACFT REQUIRED ADDITIONAL VECTORS TO REMAIN OUTSIDE OF MOB AIRSPACE. PNS CTLR ALLEGES CONTINUING PROB WITH MOB CTLRS.

Narrative: THESE ARE 2 SEPARATE EVENTS THAT OCCURRED WITHIN A FEW MINS WITH MOB APCH. ACFT #1 DEPARTED AL15, PROCEEDING NW TO THE M11 ARPT, CLBING TO 8000 FT. MOB APCH WOULD NOT TAKE THE HDOF, AND I HAD TO TURN THE ACFT TO THE NE TO REMAIN IN MY AIRSPACE. ACFT #2 WAS WBOUND, DSNDING TO 6000 FT, LNDG BFM. AGAIN, MOB APCH REFUSED TO TAKE THE HDOF. WHEN I ATTEMPTED TO SPIN THE ACFT, THE IRATE (JUSTIFIABLY) PLT CANCELED IFR. BOTH OF THE ACFT WERE ON IFR FLT PLANS, IN THE NAS SYS. THIS PROB WITH MOB APCH HAS BEEN ONGOING FOR MANY MONTHS. WE HAVE DOCUMENTED NUMEROUS OCCASIONS WHERE WE HAVE HAD TO SPIN ACRS, AIR TAXIES, CIVILIAN AND MIL BECAUSE THEY WOULD NOT ACCEPT A TIMELY HDOF. MANY OF US HAVE ALSO FILED UCR'S, TO NO AVAIL. THE CTLRS AT PNS APCH HAVE COMPLAINED FOR A LONG TIME ABOUT A PROB WE FEEL IS UNSAFE AND UNNECESSARY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR ATTRIBUTES THESE INTERMITTENT, BUT CONSTANT, EVENTS TO PERSONALITY PROBS AT MOB APCH. THE 2 ACFT DESCRIBED IN THE EVENT WERE ON APPROPRIATE, LOA AUTH ROUTINGS. AUTOMATION WAS NOT A FACTOR, AND ACFT WERE IN PROPER HDOF MODE. THE RPTR IS ALSO CONCERNED WITH OTHER 'NONSTANDARD OPERATING PRACTICES' OBSERVED WITH CERTAIN MOB APCH PERSONNEL. THESE OTHER 'PRACTICES' MAINLY FOCUS ON THE EARLY TERMINATION OF VFR ACFT AND THE ASSOCIATED AUTOMATED TRACKED FLT PLANS. THE PNS CTLR IS REQUIRED TO ASK FOR PERTINENT INFO TO REINITIATE A TRACKED FLT THAT HAD BEEN ALREADY COMPLETE IN THE COMPUTER. THOUGH SIMILAR SITS HAVE BEEN OCCURRING FOR ALMOST 2 YRS, THE RPTR STATES THAT MGMNT HAS BEEN UNABLE TO RESOLVE THESE 'PERSONALITY ISSUES' WITH MOB.

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.