Modification & STC status
Cessna Citation Longitude modification and STC status records review
This review confirms that every modification, STC, and Service Bulletin recorded against a Cessna Citation Longitude carries an approval basis and applies to this serial number. A records specialist runs it before a transaction, after a cabin or avionics upgrade, or when a configuration list has accumulated changes across successive owners. It checks each SB embodiment for the correct revision and effectivity, traces each STC to its approval and installation evidence, and maps the recorded configuration against what the type design and approved changes actually permit. You receive a validated modification status, a list of changes lacking a traceable basis or recorded against the wrong effectivity, and the approval evidence assembled behind each.
When this review is needed
- A buyer needs the installed configuration and its approval basis confirmed before pricing the aircraft.
- A cabin connectivity or avionics upgrade was fitted and its STC paperwork has not been reconciled to the configuration list.
- Successive owners each added changes and no one has checked the modification record against the type design in years.
- A Service Bulletin is claimed as embodied but the revision and effectivity behind the entry have never been verified.
The problem
A Longitude collects modifications quickly during its early ownership: connectivity systems, cabin-management upgrades, additional avionics options, interior changes an owner specifies. Each one should land in the records with its STC or approved data and its effectivity, but an upgrade fitted under a management arrangement or during a warranty-era visit often gets logged as embodied while its approval paper stays with the installer. A Service Bulletin marked complete against the wrong revision, or an STC recorded against an effectivity that does not cover this serial number, leaves the configuration list asserting a state the evidence cannot support.
What gets reviewed
- Each embodied STC traced to its approval and to the installation evidence for this serial number
- Service Bulletin embodiments checked for the correct revision and the applicable effectivity
- The approval basis and substantiation behind each recorded modification confirmed as present
- Connectivity, cabin, and avionics upgrades reconciled to the configuration list and their approved data
- Recorded configuration mapped against the type design and the manufacturer's approved change list
- Equipment changes recorded as modifications where the type requires it rather than logged as routine swaps
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 claimed STC carries approval data appropriate to the installation and to the operating jurisdiction
- Service Bulletin effectivity matches this serial number and the airframe's build and modification history
- The recorded configuration reconciles with the type design and the approved modification list
- Every upgrade on the configuration list has its installation and release evidence behind it
- A modification with no traceable basis is flagged rather than accepted on the strength of the list entry alone
Evidence normally required
- The modification and STC status list with effectivity for the serial number
- STC approval documents and the installation records that embodied them
- Service Bulletin embodiment records with the revision applied
- The type design and configuration reference for the Longitude
- Approval and substantiation data for the cabin, connectivity, and avionics changes
Common discrepancies
- An STC recorded as embodied with its approval paper still held by the installer, not the aircraft file
- A Service Bulletin marked complete against a revision that does not match the effectivity claimed
- A cabin or connectivity upgrade on the configuration list with no approved data behind it
- An equipment change logged as a routine swap where the type design treats it as a modification
What is at stake
A modification embodied without traceable approval data can force removal or re-substantiation at the worst moment, in the middle of a sale or an operator acceptance. A change recorded against the wrong effectivity corrupts the configuration baseline that AD applicability and later modifications are read against, and a Service Bulletin claimed but not evidenced can reopen a compliance question a buyer thought was closed.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the claimed configuration
Pull the STC, SB, and modification status the records assert for the serial number.
Check basis and effectivity
Confirm each change carries appropriate approval data and applies to this aircraft's effectivity.
Reconcile to type design
Map the recorded configuration against the type design and the approved change list.
List the exceptions
Flag changes lacking a traceable basis or recorded against the wrong effectivity, with the evidence behind each.
What the buyer receives
- A validated modification status tied to the type design and the serial number's effectivity
- A list of changes lacking a traceable basis or recorded against the wrong effectivity
- The approval evidence assembled behind each embodied modification and STC
Who uses the output
- Records teams setting a configuration baseline the rest of the file relies on
- Engineering deciding how to treat a modification with no traceable approval basis
- Asset and acquisition teams pricing the configuration the records can actually support
How the work fits into the transaction or program
Modification status establishes the configuration baseline that AD applicability, equipment records, and any future upgrade all read against. This review runs before a transaction or right after an upgrade so the configuration list catches up to the airframe, and its exception list feeds the remediation that recovers the approval evidence a change is missing.
Aircraft-specific considerations
A Citation Longitude carries a Garmin-based flight deck and a set of factory and aftermarket cabin and connectivity options, so its modification history concentrates in avionics software configuration and cabin systems rather than in structural or performance STCs. Those avionics changes depend on software-load records as much as hardware approvals, which is where the review looks first for a configuration entry the paper does not fully support.
Jurisdiction-specific considerations
An STC approved under the FAA does not automatically hold validity for an EASA operator, so a Longitude changing registers may carry modifications that need validated or supplemental approval before the receiving authority accepts them, and the review marks each change whose basis is jurisdiction-specific.
Regulatory limits
The review confirms the recorded configuration is internally consistent and supported by approval data. It does not approve a modification, grant or validate an STC, or determine that the aircraft is in an airworthy configuration.
What this review does not cover
- A physical configuration survey of the installed equipment
- Developing, approving, or validating new modification or STC data
- Any airworthiness determination on the installed configuration
Specific to this review
- On this type the approval paper for an aftermarket upgrade often stays with the installing shop rather than reaching the aircraft file, so a real modification can look unsupported until that document is recovered.
- Avionics configuration depends on software-load records, meaning a modification entry can be genuine while the evidence that proves its current state lives in a separate avionics folder.
- Effectivity is where the record breaks quietly: a Service Bulletin can be truly embodied but logged against a revision that does not apply to this serial number.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Frequently asked questions
The upgrades were all done at reputable shops. Why check the STC paper?
A quality installation and complete records are two different things. On a business jet the approval and installation paper frequently stays with the installer while the configuration list is updated separately, so a change can be perfectly airworthy yet unsupported in the aircraft file. The review recovers and ties that paper to the configuration so a buyer or authority can rely on 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.