AFAC's Reglamento federal mirrors much of the FAA framework with regional adaptations for Mexico's high-altitude operations and trans-border traffic. Heavy US-Mexico charter + corporate flight traffic makes AviationAlley a natural fit for cross-border operators.
MMMXAeroméxico hub + busiest airport in Latin America by passengers
MMSMFelipe Ángeles International — new capital hub for cargo + low-cost ops
MMUNMajor tourism gateway + international charter operations
MMMYNorthern industrial hub + cross-border corporate flight + Volaris base
Same operation, different label. AviationAlley's module-gating system maps cleanly onto Mexico's regulatory structure.
| US (FAA) | Mexico (Agencia) | What's similar / different |
|---|---|---|
| FAR Part 141 | AFAC Escuela de Aviación Civil | Civil aviation school certification. |
| FAR Part 142 | AFAC Centro de Adiestramiento | Sim-based training center certification. |
| FAR Part 121 | AFAC Operador Aéreo Regular | Scheduled airline operator certificate. |
| FAR Part 135 | AFAC Operador de Servicios Aéreos | Charter / on-demand operator. |
| AAIP | AFAC Programa de Mantenimiento | Maintenance program — similar to AAIP scope. |
AFAC's NOM-008 (operator certification) defines the scheduled/charter/training certificate categories. Fatigue rules are NOM-117 — derived from FAR 117 with minor adaptations for high-altitude pilot acclimatization. Cross-border operators flying US ↔ MX routes generally maintain compliance with both AFAC and FAA simultaneously; the audit log supports filtering by either authority.
Today, English-only. Spanish localization is on the roadmap for 2027. Stripe + billing handle MXN natively. Customer-facing PDF documents (quotes, invoices) can be Spanish via custom templates for enterprise customers.
Audit log filter chips support both FAA and AFAC inspector views. Pilot credentials track both FAA + AFAC licenses on the same row. Tail registration supports US (N-number) + MX (XA/XB/XC) prefixes. International charter quoting via Avinode handles MX customs requirements.
Default deployment is US-region. Mexico has no data-residency requirement; enterprise customers concerned about Article 8 LFPD compliance can request Mexico-region deployment via AWS.
Book a 30-minute call. We'll cover Agencia alignment, integration scoping for Mexico airspace data, and what enterprise hosting in Mexico looks like.