Skip to content

AD status

Cessna Citation Longitude Airworthiness Directive status records review

This review tests the Airworthiness Directive status list for a Cessna Citation Longitude and confirms that each line rests on real applicability logic and accomplishment evidence. It suits an asset manager or CAMO lead who has to stand behind AD status before a sale, a lease, or a program transfer. We check applicability against the effectivity for this serial number, trace each closed AD to its compliance record, and test how recurring items are being tracked. You receive an exception list, a source map, and a closure plan for this aircraft.

When this review is needed

  • A sale or lease is in diligence and the buyer is pricing against the AD status list.
  • The aircraft is moving to a new operator whose program will inherit every recurring AD interval.
  • The status list was produced by tracking software and nobody has tied its lines back to compliance records.
  • A recent AD was superseded and the list has not been checked for how the change flows through.

The problem

An AD status list looks definitive because it is a clean grid of numbers and dates, but each line is only a claim until the compliance record behind it is seen. On a Citation Longitude, a young type still accumulating directives, applicability turns on effectivity and configuration that the list may state without proof. A line marked complied can rest on a method of compliance that was never actually documented.

What gets reviewed

  • Applicability of each AD to this serial number against its effectivity and configuration
  • Accomplishment evidence for every AD the list records as complied with
  • Method of compliance for each item, including reference to the approved data used
  • Recurring AD intervals checked from the correct last-done point and projected forward
  • Superseded and revised directives traced through to the current status they produce
  • Coverage across airframe, the two HTF7700L engines, and appliance-level directives

Scope this review

Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.

Send a representative, redacted record set and we will scope the review.

What gets validated

  • Each AD flagged applicable matches the effectivity and installed configuration for this tail
  • Every complied line is supported by an accomplishment record naming the work and its date
  • The stated method of compliance references approved data rather than a bare assertion
  • Recurring AD next-due calculations start from a documented last accomplishment
  • Superseded directives are closed correctly and the superseding item carried on the list

Evidence normally required

  • The current AD status list from the tracking system or CAMO
  • Accomplishment records, work orders, and release documents cited by the list
  • Effectivity and configuration data establishing applicability for this serial number
  • Engine AD status for the two HTF7700L positions and appliance directives
  • Any manufacturer or authority correspondence on superseded or revised directives

Common discrepancies

  • An AD marked complied with no accomplishment record naming the work behind it
  • Applicability accepted from the list without the effectivity data that would confirm it
  • A recurring AD whose next-due date is calculated from an undocumented last accomplishment
  • A superseded directive left open while its replacement is missing from the list

What is at stake

An unsupported AD line does not stay hidden. It surfaces at the worst moment, during a transfer or an authority review, and forces the holder to prove compliance retroactively or accomplish the directive again. A recurring AD tracked from the wrong start point can put the aircraft out of interval without anyone realizing, which grounds it until the record is rebuilt.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Confirm applicability

Test each AD against the effectivity and configuration for this serial number before assessing its status.

02

Trace accomplishment

Match every complied line to an accomplishment record and the approved data behind the method of compliance.

03

Recompute recurring items

Rebuild next-due dates for recurring ADs from a documented last accomplishment and flag any drift.

04

Report and sequence

Deliver the exception list, source map, and a closure plan ordered by consequence.

What the buyer receives

  • An exception list ranking each unsupported or miscalculated AD line by its consequence
  • A source map linking every AD line to the accomplishment record and approved data behind it
  • A closure plan naming the evidence needed to make each open line defensible

Who uses the output

  • Asset managers who need AD status they can defend in a transaction
  • CAMO leads inheriting the recurring AD program on transfer
  • Buyers pricing residual value and compliance risk from the status list

How the work fits into the transaction or program

AD status is one of the first things any counterparty reads and one of the hardest to reconstruct after the fact. This review confirms the list before it drives a price or a program handover, and it feeds directly into the recurring-item tracking the receiving operator will maintain. It pairs with LLP and shop-visit reviews to give a full compliance picture for the serial number.

Aircraft-specific considerations

The Citation Longitude entered service recently, so its AD population is still growing and skews toward avionics and system directives tied to the G5000 flight deck and the two HTF7700L engines. Many airframes are still inside owner-handover and warranty-era records, which means early modifications embodied under warranty can shift applicability in ways the status list does not always capture without a configuration check.

Jurisdiction-specific considerations

An FAA-registered Citation Longitude tracks FAA Airworthiness Directives, while an EASA operator must also account for EASA ADs and any that mandate different terms. On a cross-border transfer, the AD status list has to be re-read against the receiving authority's directives, since a list complete under one authority can leave open items under another.

Regulatory limits

This review reports on whether AD status is supported by evidence. It does not determine airworthiness, grant or approve any method of compliance, accomplish any directive, or replace the CAMO or operator responsible for AD management.

What this review does not cover

Specific to this review

  • A tracking-system AD list is a summary, not evidence; each line stays a claim until the accomplishment record behind it is produced.
  • The most damaging error is a recurring AD calculated from an undocumented last-done date, because it can silently drift out of interval.
  • On a young type like the Longitude the AD population is still growing, so a list correct last quarter can already be missing a newly issued directive.
  • Warranty-era modifications can change AD applicability, so applicability must be tested against configuration rather than read off the list.

Sources

Frequently asked questions

Our tracking software already produces an AD status list. Why review it?

The software reports what was entered into it, not what the compliance records prove. If an accomplishment was logged without its supporting document, or a recurring interval was started from the wrong date, the list still looks clean. This review ties each line back to source so an unsupported claim surfaces before a buyer or an authority finds it.

Relevant glossary terms

Related pages

Where this fits

Talk to an engineer who has done this work

We will walk through your current state, the records or evidence involved, and a scoped first engagement.

Talk through the aircraft, records, evidence, deadline, and next useful step.