AMO management

Published 7 October 2026, Updated 7 October 2026

Select A.M.O below the main tabs or Manage A.M.O from a resource menu. The grid shows creation date, AMO name, license, contact, email, inactive state, and number of allocated resources. Additional form fields include address, phone, cell, and internal note.

[SCREENSHOT: maintenance-amo-manager | Capture: Aircraft Maintenance Organizations dialog with grid, pager actions, inactive and allocated-resource columns.]

19.1 Add an AMO

1. Select Add.
2. Enter the AMO name; it is required.
3. Enter license, address, main phone, contact, email, cell, and note as applicable.
4. Save.
5. Refresh and confirm the AMO appears in resource assignment menus.

Invalid phone values can be cleared by the form. Re-enter them in a valid international/national format before saving.

[SCREENSHOT: maintenance-amo-add | Capture: Add AMO form with every visible field and save/cancel controls.]

[SCREENSHOT: maintenance-amo-add-validation | Capture: Required-name or invalid-phone feedback.]

19.2 Edit or view an AMO

Select the row and use Edit to update contact details or View for a read-only review. Changes are retained in the AMO’s history for accountability.

[SCREENSHOT: maintenance-amo-edit | Capture: Edit AMO form showing address, phone, contact, email, cell, and note.]

[SCREENSHOT: maintenance-amo-view | Capture: Read-only AMO view dialog.]

19.3 Delete or make an AMO inactive

Select the AMO and choose Delete.

• If it has never been assigned to an aircraft, it can be deleted.
• If it is currently assigned or has ever been used, it is preserved and marked inactive.
• An inactive AMO is removed from new assignment choices while historical visit information remains understandable.

If an AMO changes its legal identity, follow the organization’s record-control policy rather than overwriting history in a misleading way.

[SCREENSHOT: maintenance-amo-delete-confirm | Capture: Delete confirmation for an AMO.]

[SCREENSHOT: maintenance-amo-inactive-result | Capture: Previously used AMO retained with inactive lock and allocation/history context.]