Your Records Are Your Reliability Program

Dispatch reliability, AOG recovery, and predictive maintenance all sit on top of one substrate: clean, queryable, traceable records. The AOG Technics scandal proved that possessing an 8130-3 isn't the same as verifying it.

Israel Slodowitz

Israel Slodowitz

Founder of Radar

Maintenance & Reliability

|

The Number That Hides the Other Number

Ask a director of maintenance how the fleet is performing and you will usually hear a dispatch reliability figure: 99.5, 99.6, maybe 99.7 percent. It is a genuinely good number, and it is roughly where well-run business-jet programs land. The trouble is that dispatch reliability answers a narrow question. It measures the percentage of scheduled departures that left without a maintenance-caused delay or cancellation beyond some threshold. It tells you almost nothing about how many days the aircraft was simply not available to fly.

Those are two different metrics, and conflating them is one of the more expensive analytical errors in this business. An aircraft can post 99.6 percent dispatch reliability and still rack up 25 down-days a year, because the down-days accumulate outside the dispatch window. A part sits on backorder while the airplane waits. A scheduled inspection runs three days long because nobody could locate the last task card. An AOG resolves in eight hours of wrench-turning but takes two days because the paperwork to release the part could not be verified. Dispatch reliability measures the moments you tried to fly; operational availability measures the calendar. High reliability can mask real availability losses, and the gap between the two almost always traces back to the same place, which is the records.

Anatomy of an 8130-3, and the Misconception Inside It

The FAA Form 8130-3 Authorized Release Certificate, along with its EASA Form 1 counterpart, is the document that travels with a part and asserts its airworthiness. Most people in a hangar can find the form. Far fewer read it correctly, and the misreads are exactly where risk hides. Block 11 is the status field, and it carries more weight than most installers give it credit for, because "new," "overhauled," "inspected," and "repaired" are not interchangeable. Each implies a different maintenance history and a different basis for the release. Block 12 carries the remarks that qualify everything above, including the all-important reference to the data the work was performed against, and Block 3 carries the form tracking number, which is the thread you pull to connect the certificate back to a work order, a serial number, and ultimately the back-to-birth chain.

The distinction that genuinely trips people is the one between Block 13a and Block 14a. Block 13a certifies conformity to approved design data and condition for safe operation under the certifying authority's rules; Block 14a is the return-to-service certification under the applicable maintenance regulations. A tag can be signed in one block and not the other, and which block is signed changes what the document actually authorizes. None of this, however, gets at the misconception worth naming plainly: a valid 8130-3 does not authorize installation on your specific aircraft. The tag certifies the part's airworthiness status at the moment of release. It says nothing about eligibility for your make and model, your configuration, your STC environment, or the AD and SB posture of the airframe receiving it. Eligibility is a separate determination the installer has to make. A clean tag and a wrong part number can coexist quite happily, and an installer who treats possession of the form as the end of the inquiry has skipped the actual job.

Possession Is Not Verification

For a long time the industry treated a present, properly completed 8130-3 as sufficient on its own. The AOG Technics affair ended that complacency. Across 2023, investigators tied more than 70,000 suspect unapproved parts to forged EASA Form 1 and FAA 8130-3 documentation, a large share of it for CFM56 engine components, the powerplant under a huge fraction of the world's narrowbody fleet. In many cases the hardware was real; the paperwork attesting to its provenance and condition was fabricated. Operators had the tags. The tags were lies.

What turned the episode from a back-shop curiosity into a board-level concern is what it forced everyone to confront, which is that the certificate had quietly become the object of trust, and the certificate could be faked. The only real defense is verification against the issuing organization and the underlying records rather than inspection of the paper itself. In practice that means being able to ask, for any part installed anywhere in your fleet, who issued the release, whether that organization actually exists and holds the approval it claims, and whether the serial and work-order chain reconciles from end to end. An operator who can answer that in minutes has a reliability program. An operator who keeps tags in a three-ring binder and trusts them has an exposure that no insurance rider fully covers and that surfaces at the worst possible moment, which is usually a pre-purchase inspection or an engine shop visit years later.

The First Hours of an AOG Are Spent Looking for Paper

Quantify a ground event honestly and the cost structure is brutal. Depending on the airframe, the mission, and whether you have passengers stranded at an FBO waiting on a charter recovery, an AOG runs somewhere between roughly $10,000 and $150,000 an hour in direct and consequential cost. The instinct is to assume that money buys wrench time. Often it buys search time instead.

The opening hours of a serious ground event are frequently spent not diagnosing or repairing but locating documents: the dirty-fingerprint history of the suspect component, the last shop visit records, the trace package for the spare sitting in the parts room, and the AD compliance status that determines whether the swap even returns the aircraft to a conforming state. When those records are scattered across a maintenance tracking system, a shop's email archive, a binder in a filing cabinet, and a vendor's server, the clock runs at full rate while people make phone calls. A single unverifiable 8130-3 on the spare you intended to install can extend the event by days, because now you are sourcing a second part and re-establishing its trace from scratch while the first airplane sits. The MEL might buy you a few legs of relief if the failed item happens to be deferrable, but a non-deferrable item plus a questionable spare is precisely the combination that turns an afternoon fix into a lost weekend.

Reactive Versus Predictive Is a Records Question

The same substrate that shortens an AOG is what makes predictive maintenance work at all. Take a flap-drive anomaly. In the reactive world, the asymmetry or the actuator-current trend goes unnoticed until the system faults in service, which means a diversion, a disrupted trip, an unplanned AOG at an off-base station, and a scramble to find both the motor and a defensible trace package for it. In the predictive world, flight-data trend monitoring flags the drive motor's signature drifting across a dozen cycles before it reaches a fault threshold.

That early warning is only useful if you can immediately answer the next three questions: do we have a documented spare with a verified release certificate, what is its time-since-overhaul against the applicable TBO, and is it eligible for this tail. With queryable records, the motor and its paperwork get staged together and the swap happens on a scheduled visit, on the ground, on your calendar. Without them, the trend data is just an interesting chart, because you cannot act on a prediction you cannot supply. Prediction without provenance is a guess with better graphics, and a maintenance program that cannot connect a forecast to a verified, eligible part on the shelf is still a reactive program wearing a dashboard.

One Record Set, Four Readers

The through-line here is that a single query serves nearly everyone who ever asks hard questions about the fleet. "Show me every part installed in the last five years, with its release certificate and issuing organization" is the question a DOM asks during an AOG, an auditor asks during a compliance review, a buyer's technical representative asks during a pre-buy, and a lender's appraiser asks before funding. It is one question with four audiences, and the operator who can answer it in plain English answers all four at once. The same logbook gaps that generate an audit finding also depress residual value at resale and stall a predictive program before it produces a single useful prediction.

That is the quiet argument for treating records as infrastructure rather than as a filing obligation. When every logbook, manual, STC, and FAA document across the fleet is digitized, connected, and actually queryable, reliability stops being a number you report once a month and becomes a property you can verify on demand. The records are not the paperwork wrapped around your reliability program. They are the program.

Your fleet's records at your fingertips.

Sign up, print a label, and search your first tail within days. Free.

Get Started Free

Your Records Are Your Reliability Program

Dispatch reliability, AOG recovery, and predictive maintenance all sit on top of one substrate: clean, queryable, traceable records. The AOG Technics scandal proved that possessing an 8130-3 isn't the same as verifying it.

Israel Slodowitz

Israel Slodowitz

Founder of Radar

Maintenance & Reliability

|

The Number That Hides the Other Number

Ask a director of maintenance how the fleet is performing and you will usually hear a dispatch reliability figure: 99.5, 99.6, maybe 99.7 percent. It is a genuinely good number, and it is roughly where well-run business-jet programs land. The trouble is that dispatch reliability answers a narrow question. It measures the percentage of scheduled departures that left without a maintenance-caused delay or cancellation beyond some threshold. It tells you almost nothing about how many days the aircraft was simply not available to fly.

Those are two different metrics, and conflating them is one of the more expensive analytical errors in this business. An aircraft can post 99.6 percent dispatch reliability and still rack up 25 down-days a year, because the down-days accumulate outside the dispatch window. A part sits on backorder while the airplane waits. A scheduled inspection runs three days long because nobody could locate the last task card. An AOG resolves in eight hours of wrench-turning but takes two days because the paperwork to release the part could not be verified. Dispatch reliability measures the moments you tried to fly; operational availability measures the calendar. High reliability can mask real availability losses, and the gap between the two almost always traces back to the same place, which is the records.

Anatomy of an 8130-3, and the Misconception Inside It

The FAA Form 8130-3 Authorized Release Certificate, along with its EASA Form 1 counterpart, is the document that travels with a part and asserts its airworthiness. Most people in a hangar can find the form. Far fewer read it correctly, and the misreads are exactly where risk hides. Block 11 is the status field, and it carries more weight than most installers give it credit for, because "new," "overhauled," "inspected," and "repaired" are not interchangeable. Each implies a different maintenance history and a different basis for the release. Block 12 carries the remarks that qualify everything above, including the all-important reference to the data the work was performed against, and Block 3 carries the form tracking number, which is the thread you pull to connect the certificate back to a work order, a serial number, and ultimately the back-to-birth chain.

The distinction that genuinely trips people is the one between Block 13a and Block 14a. Block 13a certifies conformity to approved design data and condition for safe operation under the certifying authority's rules; Block 14a is the return-to-service certification under the applicable maintenance regulations. A tag can be signed in one block and not the other, and which block is signed changes what the document actually authorizes. None of this, however, gets at the misconception worth naming plainly: a valid 8130-3 does not authorize installation on your specific aircraft. The tag certifies the part's airworthiness status at the moment of release. It says nothing about eligibility for your make and model, your configuration, your STC environment, or the AD and SB posture of the airframe receiving it. Eligibility is a separate determination the installer has to make. A clean tag and a wrong part number can coexist quite happily, and an installer who treats possession of the form as the end of the inquiry has skipped the actual job.

Possession Is Not Verification

For a long time the industry treated a present, properly completed 8130-3 as sufficient on its own. The AOG Technics affair ended that complacency. Across 2023, investigators tied more than 70,000 suspect unapproved parts to forged EASA Form 1 and FAA 8130-3 documentation, a large share of it for CFM56 engine components, the powerplant under a huge fraction of the world's narrowbody fleet. In many cases the hardware was real; the paperwork attesting to its provenance and condition was fabricated. Operators had the tags. The tags were lies.

What turned the episode from a back-shop curiosity into a board-level concern is what it forced everyone to confront, which is that the certificate had quietly become the object of trust, and the certificate could be faked. The only real defense is verification against the issuing organization and the underlying records rather than inspection of the paper itself. In practice that means being able to ask, for any part installed anywhere in your fleet, who issued the release, whether that organization actually exists and holds the approval it claims, and whether the serial and work-order chain reconciles from end to end. An operator who can answer that in minutes has a reliability program. An operator who keeps tags in a three-ring binder and trusts them has an exposure that no insurance rider fully covers and that surfaces at the worst possible moment, which is usually a pre-purchase inspection or an engine shop visit years later.

The First Hours of an AOG Are Spent Looking for Paper

Quantify a ground event honestly and the cost structure is brutal. Depending on the airframe, the mission, and whether you have passengers stranded at an FBO waiting on a charter recovery, an AOG runs somewhere between roughly $10,000 and $150,000 an hour in direct and consequential cost. The instinct is to assume that money buys wrench time. Often it buys search time instead.

The opening hours of a serious ground event are frequently spent not diagnosing or repairing but locating documents: the dirty-fingerprint history of the suspect component, the last shop visit records, the trace package for the spare sitting in the parts room, and the AD compliance status that determines whether the swap even returns the aircraft to a conforming state. When those records are scattered across a maintenance tracking system, a shop's email archive, a binder in a filing cabinet, and a vendor's server, the clock runs at full rate while people make phone calls. A single unverifiable 8130-3 on the spare you intended to install can extend the event by days, because now you are sourcing a second part and re-establishing its trace from scratch while the first airplane sits. The MEL might buy you a few legs of relief if the failed item happens to be deferrable, but a non-deferrable item plus a questionable spare is precisely the combination that turns an afternoon fix into a lost weekend.

Reactive Versus Predictive Is a Records Question

The same substrate that shortens an AOG is what makes predictive maintenance work at all. Take a flap-drive anomaly. In the reactive world, the asymmetry or the actuator-current trend goes unnoticed until the system faults in service, which means a diversion, a disrupted trip, an unplanned AOG at an off-base station, and a scramble to find both the motor and a defensible trace package for it. In the predictive world, flight-data trend monitoring flags the drive motor's signature drifting across a dozen cycles before it reaches a fault threshold.

That early warning is only useful if you can immediately answer the next three questions: do we have a documented spare with a verified release certificate, what is its time-since-overhaul against the applicable TBO, and is it eligible for this tail. With queryable records, the motor and its paperwork get staged together and the swap happens on a scheduled visit, on the ground, on your calendar. Without them, the trend data is just an interesting chart, because you cannot act on a prediction you cannot supply. Prediction without provenance is a guess with better graphics, and a maintenance program that cannot connect a forecast to a verified, eligible part on the shelf is still a reactive program wearing a dashboard.

One Record Set, Four Readers

The through-line here is that a single query serves nearly everyone who ever asks hard questions about the fleet. "Show me every part installed in the last five years, with its release certificate and issuing organization" is the question a DOM asks during an AOG, an auditor asks during a compliance review, a buyer's technical representative asks during a pre-buy, and a lender's appraiser asks before funding. It is one question with four audiences, and the operator who can answer it in plain English answers all four at once. The same logbook gaps that generate an audit finding also depress residual value at resale and stall a predictive program before it produces a single useful prediction.

That is the quiet argument for treating records as infrastructure rather than as a filing obligation. When every logbook, manual, STC, and FAA document across the fleet is digitized, connected, and actually queryable, reliability stops being a number you report once a month and becomes a property you can verify on demand. The records are not the paperwork wrapped around your reliability program. They are the program.

Your fleet's records at your fingertips.

Sign up, print a label, and search your first tail within days. Free.

Get Started Free

Your Records Are Your Reliability Program

Dispatch reliability, AOG recovery, and predictive maintenance all sit on top of one substrate: clean, queryable, traceable records. The AOG Technics scandal proved that possessing an 8130-3 isn't the same as verifying it.

Israel Slodowitz

Israel Slodowitz

Founder of Radar

Maintenance & Reliability

|

The Number That Hides the Other Number

Ask a director of maintenance how the fleet is performing and you will usually hear a dispatch reliability figure: 99.5, 99.6, maybe 99.7 percent. It is a genuinely good number, and it is roughly where well-run business-jet programs land. The trouble is that dispatch reliability answers a narrow question. It measures the percentage of scheduled departures that left without a maintenance-caused delay or cancellation beyond some threshold. It tells you almost nothing about how many days the aircraft was simply not available to fly.

Those are two different metrics, and conflating them is one of the more expensive analytical errors in this business. An aircraft can post 99.6 percent dispatch reliability and still rack up 25 down-days a year, because the down-days accumulate outside the dispatch window. A part sits on backorder while the airplane waits. A scheduled inspection runs three days long because nobody could locate the last task card. An AOG resolves in eight hours of wrench-turning but takes two days because the paperwork to release the part could not be verified. Dispatch reliability measures the moments you tried to fly; operational availability measures the calendar. High reliability can mask real availability losses, and the gap between the two almost always traces back to the same place, which is the records.

Anatomy of an 8130-3, and the Misconception Inside It

The FAA Form 8130-3 Authorized Release Certificate, along with its EASA Form 1 counterpart, is the document that travels with a part and asserts its airworthiness. Most people in a hangar can find the form. Far fewer read it correctly, and the misreads are exactly where risk hides. Block 11 is the status field, and it carries more weight than most installers give it credit for, because "new," "overhauled," "inspected," and "repaired" are not interchangeable. Each implies a different maintenance history and a different basis for the release. Block 12 carries the remarks that qualify everything above, including the all-important reference to the data the work was performed against, and Block 3 carries the form tracking number, which is the thread you pull to connect the certificate back to a work order, a serial number, and ultimately the back-to-birth chain.

The distinction that genuinely trips people is the one between Block 13a and Block 14a. Block 13a certifies conformity to approved design data and condition for safe operation under the certifying authority's rules; Block 14a is the return-to-service certification under the applicable maintenance regulations. A tag can be signed in one block and not the other, and which block is signed changes what the document actually authorizes. None of this, however, gets at the misconception worth naming plainly: a valid 8130-3 does not authorize installation on your specific aircraft. The tag certifies the part's airworthiness status at the moment of release. It says nothing about eligibility for your make and model, your configuration, your STC environment, or the AD and SB posture of the airframe receiving it. Eligibility is a separate determination the installer has to make. A clean tag and a wrong part number can coexist quite happily, and an installer who treats possession of the form as the end of the inquiry has skipped the actual job.

Possession Is Not Verification

For a long time the industry treated a present, properly completed 8130-3 as sufficient on its own. The AOG Technics affair ended that complacency. Across 2023, investigators tied more than 70,000 suspect unapproved parts to forged EASA Form 1 and FAA 8130-3 documentation, a large share of it for CFM56 engine components, the powerplant under a huge fraction of the world's narrowbody fleet. In many cases the hardware was real; the paperwork attesting to its provenance and condition was fabricated. Operators had the tags. The tags were lies.

What turned the episode from a back-shop curiosity into a board-level concern is what it forced everyone to confront, which is that the certificate had quietly become the object of trust, and the certificate could be faked. The only real defense is verification against the issuing organization and the underlying records rather than inspection of the paper itself. In practice that means being able to ask, for any part installed anywhere in your fleet, who issued the release, whether that organization actually exists and holds the approval it claims, and whether the serial and work-order chain reconciles from end to end. An operator who can answer that in minutes has a reliability program. An operator who keeps tags in a three-ring binder and trusts them has an exposure that no insurance rider fully covers and that surfaces at the worst possible moment, which is usually a pre-purchase inspection or an engine shop visit years later.

The First Hours of an AOG Are Spent Looking for Paper

Quantify a ground event honestly and the cost structure is brutal. Depending on the airframe, the mission, and whether you have passengers stranded at an FBO waiting on a charter recovery, an AOG runs somewhere between roughly $10,000 and $150,000 an hour in direct and consequential cost. The instinct is to assume that money buys wrench time. Often it buys search time instead.

The opening hours of a serious ground event are frequently spent not diagnosing or repairing but locating documents: the dirty-fingerprint history of the suspect component, the last shop visit records, the trace package for the spare sitting in the parts room, and the AD compliance status that determines whether the swap even returns the aircraft to a conforming state. When those records are scattered across a maintenance tracking system, a shop's email archive, a binder in a filing cabinet, and a vendor's server, the clock runs at full rate while people make phone calls. A single unverifiable 8130-3 on the spare you intended to install can extend the event by days, because now you are sourcing a second part and re-establishing its trace from scratch while the first airplane sits. The MEL might buy you a few legs of relief if the failed item happens to be deferrable, but a non-deferrable item plus a questionable spare is precisely the combination that turns an afternoon fix into a lost weekend.

Reactive Versus Predictive Is a Records Question

The same substrate that shortens an AOG is what makes predictive maintenance work at all. Take a flap-drive anomaly. In the reactive world, the asymmetry or the actuator-current trend goes unnoticed until the system faults in service, which means a diversion, a disrupted trip, an unplanned AOG at an off-base station, and a scramble to find both the motor and a defensible trace package for it. In the predictive world, flight-data trend monitoring flags the drive motor's signature drifting across a dozen cycles before it reaches a fault threshold.

That early warning is only useful if you can immediately answer the next three questions: do we have a documented spare with a verified release certificate, what is its time-since-overhaul against the applicable TBO, and is it eligible for this tail. With queryable records, the motor and its paperwork get staged together and the swap happens on a scheduled visit, on the ground, on your calendar. Without them, the trend data is just an interesting chart, because you cannot act on a prediction you cannot supply. Prediction without provenance is a guess with better graphics, and a maintenance program that cannot connect a forecast to a verified, eligible part on the shelf is still a reactive program wearing a dashboard.

One Record Set, Four Readers

The through-line here is that a single query serves nearly everyone who ever asks hard questions about the fleet. "Show me every part installed in the last five years, with its release certificate and issuing organization" is the question a DOM asks during an AOG, an auditor asks during a compliance review, a buyer's technical representative asks during a pre-buy, and a lender's appraiser asks before funding. It is one question with four audiences, and the operator who can answer it in plain English answers all four at once. The same logbook gaps that generate an audit finding also depress residual value at resale and stall a predictive program before it produces a single useful prediction.

That is the quiet argument for treating records as infrastructure rather than as a filing obligation. When every logbook, manual, STC, and FAA document across the fleet is digitized, connected, and actually queryable, reliability stops being a number you report once a month and becomes a property you can verify on demand. The records are not the paperwork wrapped around your reliability program. They are the program.

Your fleet's records at your fingertips.

Sign up, print a label, and search your first tail within days. Free.

Get Started Free