Developer ToolsFree generatorPDF, Excel, Word exportAerospace MRO

Aircraft Component Removal and Installation Record JSON Generator

Every component move needs a record: what came off, from where, with how many hours and cycles, and who released it. This generator gives you a consistent JSON payload that you can adapt for imports, API tests or integration design.

Fill in

Event type

Aircraft registration

Part number

Serial number

Position

ATA chapter

Time since new (hours)

Cycles since new

Aircraft total hours at event

Removal reason

Event date

Released by (authorisation no.)

Generated code

Download:

JSON payload

{
  "eventType": "REMOVAL",
  "eventDate": "2026-10-20",
  "aircraft": {
    "registration": "N123AB",
    "totalHours": 32480
  },
  "component": {
    "partNumber": "3214-5-002",
    "serialNumber": "SN-884219",
    "position": "ENG 1 FUEL PUMP",
    "ataChapter": "73",
    "timeSinceNewHours": 18450,
    "cyclesSinceNew": 9210
  },
  "reason": "Unscheduled",
  "releasedBy": "CERT-4471"
}

curl example (replace host and token)

curl -X POST "https://maintenance.example.com/api/component-events" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d @component-event.json

Field names are an example structure, not a published standard. Match them to your maintenance system or ERP API, and add fields for location, reason codes or document references your process requires. Numeric fields are emitted without quotes, so leave them as digits.

MRO integration design review

Optional review of how component events move between your shop systems and ERP.

Optional. The tool and every export work without this. No spam.

How to use it

Choose the event type, then fill in the aircraft registration, part and serial number, position, ATA chapter and the life counters. Copy the JSON into your API client, a test file or an import specification. The second block shows a command line example so developers can try a call quickly. Because the structure is generic, rename keys to suit your target system before using it in production.

One event per payload keeps retries simple
Keep part and serial numbers as text
Send dates in ISO 8601 form

What a traceable record needs

Traceability depends on being able to follow a serialised unit from the aircraft it came off to the shop that repaired it and the aircraft it went onto. At minimum that means part number, serial number, position, event date, aircraft identity, life counters and the authorised person behind the event. For life limited parts add the back to birth reference and the limit used. Missing counters at removal are the usual reason that a part cannot be reused without extra investigation.

Common mistakes

Developers often send serial numbers as numbers, which strips leading zeros, or send aircraft hours in the wrong unit, such as hours and minutes as a decimal. Another frequent problem is missing idempotency: a retried call creates a second removal event. Add a unique event reference and make the receiving system reject duplicates. Finally, do not write back to an authoritative maintenance record without a human approval step.

Treat serial numbers as strings
Agree one unit for hours (decimal hours or hours and minutes)
Add a unique event id for safe retries

Frequently Asked Questions

Is this an industry standard format?

No. It is an illustrative structure. Aviation data exchange standards exist, such as ATA Spec 2000 and iSpec 2200 messages, but most APIs use their own field names. Use this as a starting design and map it to your target system.

Why are some values unquoted?

Numeric fields like hours and cycles are numbers in JSON, so they have no quotes. Text fields such as part and serial numbers are quoted to preserve leading zeros and letters.

Can I use it for installation events?

Yes. Set the event type to INSTALLATION and fill in the counters of the unit at the time it is fitted. Pair it with the matching removal event so the history stays continuous.

Does this satisfy regulatory record keeping?

It only structures the data. Regulatory records have required content and retention rules set by your authority and your approved procedures, so confirm them with your quality department.

If you need to connect shop floor events to an ERP or maintenance system, we can help design and build the integration with human approval on any write-back.

Talk to an Expert Explore More Free Tools

Related Tools

Aerospace & Defense

More Developer Tools tools

See all

Back to All Tools