Narrative:

I'm making a continuing complaint about how ZME conducts business as they control aircraft as they enter mem approach control airspace. The WX this afternoon was marginal with thunderstorm activity. Air traffic was very busy during the mixed outbound push with arrs. The main complaint is that ZME does not know mem airspace and constantly switches aircraft to the 'wrong' frequencys as they enter mem airspace. All position were open and staffed within mem approach. An inbound aircraft to a satellite airport (olv) was at 4000 ft and due east of mem airport. This altitude and location places the aircraft in a 'perfect' arrival airspace location. This aircraft 'flashed' to the east departure controller which is 'incorrect!' I called the hli low sector and told them that the aircraft was 'flashing' to the departure position instead of the appropriate arrival position. The ZME controller offered the usual excuse of 'I switch the aircraft to where the computer sends them.' the other day a different ZME sector controller responded with 'I switch them to where the 'letter' says to.' they have no idea what the correct frequency is to switch aircraft to if not a 4 corner post arrival aircraft during inbound pushes. And they only make excuses and don't care. Automation needs to be corrected and ZME controllers need to be trained to know mem airspace and the appropriate position frequencys. Aircraft both IFR and VFR call incorrect mem position and are instructed to squawk VFR codes because of busy air traffic periods. At times; position are combined and then decombined within mem approach/departure control. So; the excuse of automation does not fly. There have been times when mem approach/departure position when decombined have no idea what frequencys aircraft are on. I have seen where aircraft have been flown through localizer courses; etc; because of being placed on the wrong frequencys by ZME. 'Wrong frequencys make for unsafe situations!'

Related reports:

Google
 

Original NASA ASRS Text

Title: MEM TRACON CTLR NOTES ZME CTLR'S INCORRECT FREQ ASSIGNMENTS AND AUTOMATION HDOF ERRORS.

Narrative: I'M MAKING A CONTINUING COMPLAINT ABOUT HOW ZME CONDUCTS BUSINESS AS THEY CTL ACFT AS THEY ENTER MEM APCH CTL AIRSPACE. THE WX THIS AFTERNOON WAS MARGINAL WITH TSTM ACTIVITY. AIR TFC WAS VERY BUSY DURING THE MIXED OUTBOUND PUSH WITH ARRS. THE MAIN COMPLAINT IS THAT ZME DOES NOT KNOW MEM AIRSPACE AND CONSTANTLY SWITCHES ACFT TO THE 'WRONG' FREQS AS THEY ENTER MEM AIRSPACE. ALL POS WERE OPEN AND STAFFED WITHIN MEM APCH. AN INBOUND ACFT TO A SATELLITE ARPT (OLV) WAS AT 4000 FT AND DUE E OF MEM ARPT. THIS ALT AND LOCATION PLACES THE ACFT IN A 'PERFECT' ARR AIRSPACE LOCATION. THIS ACFT 'FLASHED' TO THE E DEP CTLR WHICH IS 'INCORRECT!' I CALLED THE HLI LOW SECTOR AND TOLD THEM THAT THE ACFT WAS 'FLASHING' TO THE DEP POS INSTEAD OF THE APPROPRIATE ARR POS. THE ZME CTLR OFFERED THE USUAL EXCUSE OF 'I SWITCH THE ACFT TO WHERE THE COMPUTER SENDS THEM.' THE OTHER DAY A DIFFERENT ZME SECTOR CTLR RESPONDED WITH 'I SWITCH THEM TO WHERE THE 'LETTER' SAYS TO.' THEY HAVE NO IDEA WHAT THE CORRECT FREQ IS TO SWITCH ACFT TO IF NOT A 4 CORNER POST ARR ACFT DURING INBOUND PUSHES. AND THEY ONLY MAKE EXCUSES AND DON'T CARE. AUTOMATION NEEDS TO BE CORRECTED AND ZME CTLRS NEED TO BE TRAINED TO KNOW MEM AIRSPACE AND THE APPROPRIATE POS FREQS. ACFT BOTH IFR AND VFR CALL INCORRECT MEM POS AND ARE INSTRUCTED TO SQUAWK VFR CODES BECAUSE OF BUSY AIR TFC PERIODS. AT TIMES; POS ARE COMBINED AND THEN DECOMBINED WITHIN MEM APCH/DEP CTL. SO; THE EXCUSE OF AUTOMATION DOES NOT FLY. THERE HAVE BEEN TIMES WHEN MEM APCH/DEP POS WHEN DECOMBINED HAVE NO IDEA WHAT FREQS ACFT ARE ON. I HAVE SEEN WHERE ACFT HAVE BEEN FLOWN THROUGH LOC COURSES; ETC; BECAUSE OF BEING PLACED ON THE WRONG FREQS BY ZME. 'WRONG FREQS MAKE FOR UNSAFE SITUATIONS!'

Data retrieved from NASA's ASRS site as of January 2009 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.