TECHNOLOGY TRACKER
Discussion is not deployment.
The tracker distinguishes research, proposals, prototypes, standards, testing, and systems actually deployed on aircraft.
RESEARCHED / TESTEDFAA engine-stand sensor research
DOT/FAA/TC-23/46, Phase 2, Volume 1 (2023), documents engine-stand tests, sensor technologies, and chemical sampling. Its research purpose includes identifying sensors with potential to detect bleed-air contaminants.
Limit: Engine-stand evidence does not establish fleet installation, certification, or performance in every operating condition.
Read the DOT research record ↗RESEARCHED / TESTEDFAA on-aircraft controlled testing
The FAA reports 2023 testing on its own 747, injecting oil and hydraulic fluid into engine and auxiliary-power-unit bleed air and collecting sensor measurements and chemical samples.
Limit: A research aircraft test is different from a monitor routinely used on airline passenger flights.
Read the FAA account ↗PROPOSED REQUIREMENT2026 monitoring legislation
The introduced House and Senate texts include air-quality monitoring equipment provisions. Proposed legislation belongs in the policy record, not the deployed-equipment category.
Read the House monitoring provisions ↗DEPLOYMENT NOT VERIFIED HEREEvidence needed for an operational entry
No routine airline-service deployment is established by the sources in this initial register. This is a limit of this review, not proof that no systems exist.
To add an operational entry, we seek a named operator and aircraft, installation and service dates, documented approval where applicable, the substances measured, and the system’s stated limitations.
How we label the evidence · October 20, 2026. These are Monitor Bleed Air’s editorial categories, not official certification levels. Research, policy, and deployment can proceed in parallel; one category does not automatically lead to another.
01 · IDEA OR PROPOSALDiscussed
A proposed approach, recommendation, or policy argument explains what someone believes should be done.
Example: Our citizen’s blueprint proposes a practical research-and-improvement cycle.
Evidence needed: A named author or institution, a dated proposal, and a public source.
What it does not establish: That a device works, is approved, or has been installed.
Read the citizen’s blueprint →02 · DOCUMENTED EVALUATIONResearched or tested
A laboratory study, prototype evaluation, engine-stand experiment, or aircraft trial records what was tested and under which conditions.
Example: FAA report DOT/FAA/TC-23/46, Phase 2, Volume 1 documents engine-stand sensor testing and chemical sampling.
Evidence needed: Methods, test conditions, substances measured, results, and limitations.
What it does not establish: Performance outside those conditions or routine airline-service use.
View the FAA research record ↗03 · FORMAL TECHNICAL OR POLICY WORKStandards or regulatory work
We identify the exact stage: committee work, a draft, a published standard, guidance, a proposed rule, a final rule, or a specific certification decision.
Example: The FAA describes participation in SAE E-31B and AC-9M work on bleed-air and cabin-air measurement.
Evidence needed: The responsible body, document identifier, date, version, scope, and legal status.
What it does not establish: That committee activity is a completed standard, or that a standard requires installation. Introduced bills are labeled separately as proposals.
Read the FAA standards-work summary ↗04 · VERIFIED SERVICE USEOperational deployment
A named system is documented as installed and used on identified aircraft in service. A research installation remains labeled as a trial.
Current entry: Routine airline-service deployment has not been established by the sources in this initial register. This does not mean that no systems exist.
Evidence needed: Operator, aircraft or fleet, system name, installation and service dates, approval where applicable, measured substances, and operating limitations.
What it does not establish: Universal adoption or a guarantee that every contaminant is detected.
Explore the source collection → What changes a classification?
We add or revise a label when a dated, traceable record supports it. A product announcement can identify a candidate for review; installation and service claims need supporting documentation. Approval claims must identify the authority and scope.
Each future entry will distinguish the date of the underlying event from the date we checked it, link to the evidence, and explain any remaining uncertainty. Conflicting records will be described rather than resolved by assumption.