Any Unknown or Unlisted Aircraft Manufacturer
Air Traffic Control Fully Certified
Communication Breakdown; Situational Awareness
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors; Procedure
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.
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.