ZAB controller expressed concern regarding ATC assignments made by mmzt controllers noting the same ...

Narrative:

I had two aircraft going to tus from mexico; aircraft X and aircraft Y both had an altitude of FL220. Aircraft Y also had an altitude of FL220; all assigned by mmzt center. Aircraft X came over the border and called me; right around vylla; descending out of FL240 for FL220. Apparently mmzt didn't issue a restriction. We are technically non-radar going back and forth over vylla between ZAB and mmzt (adequate radar coverage; no handoffs). About ten minutes later; aircraft Y came over the border. They were on a bad code; so the track didn't auto acquire in eram. Two sectors asked if I had someone coming from mmzt's airspace; I said yes; a tus lander. The limited code was seen crossing the border at FL261; violating another sectors airspace; they called me right about the same time. I radar identified them and asked the pilot if mmzt had given them a restriction. They said no; just a straight descent to FL220. I know this is being addressed but I'm adding these two instances because I want those who are looking at these systemic problems along the southern border to know that this is a ubiquitous and systemic problem.

Original NASA ASRS Text

Title: ZAB Controller expressed concern regarding ATC assignments made by MMZT controllers noting the same altitude was given to multiple aircraft; the reporter claiming continued systematic ATC problems along the Southern border.

Narrative: I had two aircraft going to TUS from Mexico; Aircraft X and Aircraft Y both had an altitude of FL220. Aircraft Y also had an altitude of FL220; all assigned by MMZT Center. Aircraft X came over the border and called me; right around VYLLA; descending out of FL240 for FL220. Apparently MMZT didn't issue a restriction. We are technically non-radar going back and forth over VYLLA between ZAB and MMZT (adequate radar coverage; no handoffs). About ten minutes later; Aircraft Y came over the border. They were on a bad code; so the track didn't auto acquire in ERAM. Two sectors asked if I had someone coming from MMZT's airspace; I said yes; a TUS lander. The limited code was seen crossing the border at FL261; violating another sectors airspace; they called me right about the same time. I RADAR identified them and asked the pilot if MMZT had given them a restriction. They said no; just a straight descent to FL220. I know this is being addressed but I'm adding these two instances because I want those who are looking at these systemic problems along the southern border to know that this is a ubiquitous and systemic problem.

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

Attributes
ACN	1087140
Time
Date	201305
Local Time Of Day	1801-2400
Place
Locale Reference	ZAB.ARTCC
State Reference	NM
Aircraft 1
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	Descent
Flight Plan	IFR
Aircraft 2
Make Model Name	Challenger CL601
Operating Under FAR Part	Part 91
Flight Phase	Descent
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy

ZAB controller expressed concern regarding ATC assignments made by mmzt controllers noting the same altitude was given to multiple aircraft; the reporter claiming continued systematic ATC problems along the southern border.