Maintenance

Whether AerScheduler finds the ADs for this organization's aircraft, readable by any member. When enabled, each aircraft lists its ADs to review. Turning it on or off is PATCH /organizations/adTracking (admin only).

The library search, the same one as the public GET /public/airworthiness-directives: an AD number or its start (2013-11) first, then ranked full-text over number, title, subject, maker, applicability and summary; when nothing ranks, every word as a substring, newest first. Without q, every AD, newest first. Paged, limit up to 100. Rows carry no text (details, summary, applicability): read one with GET /maintenance/airworthiness-directives/{adNumber}. Public federal data, so any member may search it.

Every inspection this organization has signed off, newest first, kept for the life of the aircraft.

This is the airworthiness history an inspector asks for. Readable by any member for the same reason squawks are: it is information about an aircraft somebody is about to fly.

Live reminders across the fleet, most urgent first.

Each reminder carries a computed due block , how many hours are left on the meter, or how many days until the date , so you don't have to recombine the template's interval with the aircraft's meters yourself.

Reported discrepancies. Visible to technicians, dispatchers, and administrators.

Note the resource is given as a flat resourceId here, where reservations take a nested resource: { id }. That inconsistency is real and is on the list to reconcile. Photos and PDFs are attached by sending fileNames (jpg, jpeg, png, heic, heif, or pdf, up to five). The server writes the S3 keys and returns signedUrlData for the client to POST each file to. fileUrls in the body is refused. Uploading is turned off in the public demo; a text squawk still files.

One Airworthiness Directive from the library. Accepts 2013-11-11, AD 2013-11-11 or 2007-21-14R1. supersededBy lists later ADs that replace it.

404 when it is not in the library, an ordinary answer: an AD the library does not hold is entered by hand.

How much of the AD library is loaded: the count, the oldest and newest publication dates, and whether every past year of the Federal Register backfill is in. The current year fills hourly.

Every aircraft's AD review list at once, as GET /maintenance/resources/{resourceId}/airworthiness-directives gives it for one: the organization's own aircraft and, for those who may see the shop, the customer aircraft in it. Items carry resourceId and no AD text. Owners, admins and technicians; anyone else gets 403.

One signed-off inspection, in full.

One reminder.

Marks the work done, which starts the next interval if the template repeats. POST rather than PATCH for historical reasons.

Send methodOfCompliance and mechanicName to also write a permanent compliance record, which is what 14 CFR 91.417 asks for on an Airworthiness Directive. That record is append-only and cannot be edited or removed afterwards, and it snapshots the rule's number and revision as they stood at signature. Omit them and the reminder simply rolls forward as before, keeping no history.

Photos and PDFs already on the open inspection (POST /maintenance/reminders/{id}/files) are copied onto that compliance record, then cleared so they do not follow the next cycle. Do not send fileUrls.

tachAtCompliance and hobbsAtCompliance higher than the aircraft's own (and lower on neither) are also recorded on the aircraft's meter log and move its meters; the response's aircraftTimes says so (updated, or logged for a reading older than its newest). If those readings pass another inspection that grounds the aircraft, the sign-off answers 409 MAINTENANCE_TRIGGER before anything is signed; send again with confirmMaintenanceTrigger: true.

Technicians and admins. Send either or both.

reminderSteps: this inspection's reminder steps on this one aircraft, when they should differ from the rule's: the same shape as the rule's reminderSteps, each key present here winning over the rule's. Null follows the rule again. Carried to the next cycle when it is signed off. Steps further out than one already sent this cycle are not sent after it. The reminder's steps is what applies; ownSteps is what this aircraft sets itself.

notApplicable: true marks the inspection as not applying to this aircraft (a VOR check on a VFR-only aircraft), with an optional notApplicableReason. While marked it is never warned, reminded, counted overdue or grounded, and an aircraft grounded for it alone goes back on the line. False puts it back: it is checked at once, so one already overdue grounds the aircraft and notifies straight away. Carried to the next cycle when it is signed off.

The AVIATES airworthiness inspections , annual, VOR, 100-hour, AD review, transponder, ELT and static/altimeter , plus the shop intervals that come up as often, and the registration renewal (84 calendar months from the issue date, 14 CFR 47.40, warned 180, 60 and 30 days out to the shop and the owners, never grounding by default).

Reference data, not records: nothing exists until you POST a preset's payload to /maintenance/reminders/templates like any other template. The intervals are the common case and are editable afterwards; caveat says where a default doesn't apply to every aircraft.

Every reminder template in your organization.

Adds a reminder template to your organization.

One reported discrepancy.

Resolves or reopens a squawk. This is a POST rather than a PATCH for historical reasons; an action field in the body is required.

Photos or PDFs on the OPEN reminder (packing slip, in-progress photos). Admin or technician. Copied onto the compliance record at sign-off, then cleared. Send fileNames only.

Removes one working file by its file name. Does not touch a signed compliance record.

Fetches one reminder template by id.

Changes the fields you send and leaves the rest alone.

Removes the reminder template.

Library ADs that name the aircraft's airframe, engine or propeller by maker and model, each with the decision made about it. A match means the AD is worth reading, never that it applies: applicability names serial ranges, installed parts and exceptions that only a person can check. A superseded AD is left out (review the one that replaced it) unless somebody already decided or tracks it. An AD tracked by an inspection with its number reads applies without a decision. Owners, admins and technicians; anyone else gets 403.

Discrepancies against one resource.

Appends one note to the squawk's thread, for recording progress on a defect without closing it. Technicians and administrators only, matching who may verify or resolve one. Notes are append-only: there is no edit and no delete, and a mistake is corrected by adding another note. A photo or PDF may stand in for text: body may be empty when fileNames is present. Read them back on the squawk itself, which returns comments oldest first.

Record that the AD applies, or that it does not and why. reason is required with not_applicable; note is required with reason other. Records who decided and when, and writes the audit trail. Returns the aircraft's list as GET does.

Puts the AD back on the aircraft's review list. Returns the list as GET does.