From a public record to a sales conversation: one real example, every link live

On 12 August 2026 the FAA published a new certification requirement for a helicopter that one company is converting from mechanical flight controls to fly-by-wire. Below is that document, what it tells you about who is about to spend money and on what, and the short email it produces. Every source link is live, so you can open each one and check the whole chain in about four minutes.

We are a publisher for aerospace and defense. We sell companies a channel on our titles for their own announcements and their people's pieces, labelled as theirs. Reading public records like this one is the work the titles are built on.

The worked example

One record, taken from the public register on 13 August 2026.

The record

On 12 August 2026 the FAA published final special conditions for the Robinson Helicopter Company Model R66 helicopter as modified by Skyryse, covering flight control system annunciation of control. Docket No. FAA-2025-5245, Special Conditions No. 25-895-SC, at 91 FR 52002. Effective 11 September 2026.

Open it: Special Conditions: Skyryse, Robinson Helicopter Company Model R66 Helicopter; Flight Control System Annunciation of Control

The checked excerpt, quoted from that document:

"On April 10, 2023, Skyryse applied for a supplemental type certificate (STC) for replacing the current mechanical primary flight controls with an FBW flight control system (FCS) in the Robinson Model R66 helicopter."

And, on why the FAA had to write a new standard at all:

"Section 27.695 was issued in 1964 for rotorcraft with rudimentary mechanical systems. The state of technology at that time provided no basis for a digital replacement."

Both strings were re-fetched from the source and confirmed present on 13 August 2026.

What it means commercially

A special condition is a rule the FAA writes when the existing airworthiness standards do not cover the design in front of them. It becomes part of the certification basis for the modification. The gap here is stated in the document itself: the 1964 rule assumes a pilot feels the aircraft through mechanical linkages. A fly-by-wire system removes that feedback, so the FAA now requires the commanded control positions and the state of the system to be displayed instead.

Commercially, it means the certification basis for this modification is being assembled one published gap at a time, on a docket anyone can read. Every gap closed moves the project closer to a supplemental type certificate. That approval is the moment a modification stops being a programme and becomes something an owner can buy.

A second reading appears when you line up the whole series. Three final special conditions have now been issued on this modification: interaction of systems and structures on 13 December 2024, static longitudinal stability on 6 May 2026, and annunciation of control on 12 August 2026. The most recent one was adopted as proposed, with a single commenter who, in the FAA's words, "stated general disagreement without explanation and without requesting a change to the proposed special conditions." Three closures and an uncontested adoption usually mean a certification basis is being closed out.

Who just acquired a problem, and why

The record fixes the shape of the problem, and the shape tells you the role it lands on.

A supplemental type certificate does not create a market. It sells into one that is already flying, because an STC modifies an aircraft that already holds a type certificate - here, the R66 fleet under Type Certificate No. R00015LA. The operators, dealers and maintenance organisations who would buy this are the same names before and after the approval. So the buyer list can be built now. The time between a certification basis closing out and a product going on sale is when that list gets built calmly. After the approval it gets built in a hurry.

The problem lands on whoever owns revenue. Depending on the company, that is a VP of sales, a chief commercial officer, a marketing lead measured on revenue, or, at this stage, sometimes still a founder. The certification side has been running a public, dated, documented process since April 2023. The commercial side gets no such docket. Somebody has to decide which operators to approach, and in what order. That is the reason to write, and it is the only reason to write.

The note

Subject: your R66 special conditions, 12 August

The FAA published the annunciation-of-control special conditions for the R66 on 12 August, effective 11 September. Third final special condition on this certification project since December 2024.

A supplemental type certificate sells into a fleet that already exists, so the buyer list is knowable now rather than after the approval.

Who owns that list at your end?

Reuben

Fifty-eight words. One event, with its source above it. One inference, offered as an inference. One question that can be answered in a line. No attachment, no calendar link, no services, and no paragraph about us.

Every factual claim in it traces to the document linked above, and nothing in it came from anywhere else.

The note is what a sales team would send. We send nothing on a customer's behalf as part of a channel; writing to a company's prospects for it is custom work, quoted in writing, and every note goes through the export review before it leaves.

The rules that make it trustworthy

Five, applied without exception.

1. A signal is a dated event about a named company, with a live source URL and a checked excerpt. Signal is our word for an event like the one above, and it is defined on the measurement standard.
2. No source URL, no row. A signal with no live source is deleted, not flagged for later. A company reached on an event that did not happen is worse than a company never reached.
3. The excerpt is a quote, checked against the source. Before a row is used, the source is fetched again and the quoted text is confirmed still present. If it is not, the row is dropped.
4. Sixty days or it is out. An older event does not enter the list, whatever else is attractive about it.
5. Ninety days between contacts. A company contacted in the last ninety days is not contacted again, whatever the record says.

No score overrides these.

Where these records live, including the parts that do not work

Every source below was checked directly on 13 August 2026.

The Federal Register API is clean, free and same-day. https://www.federalregister.gov/api/v1/documents.json, filtered to the FAA, returns JSON with no key. The special condition above was retrievable the day after publication. Airworthiness directives, special conditions, technical standard orders, exemptions and policy notices all arrive through it. It gives the most useful records in the set for the least effort.

The FAA aircraft registry is a 73MB file you download whole and compare day to day. https://registry.faa.gov/database/ReleasableAircraft.zip returned Last-Modified: Thu, 13 Aug 2026 04:57:26 GMT and a length of 72,948,947 bytes when checked on 13 August 2026, so it is genuinely daily. It rejects a plain scripted request with HTTP 403 and serves the same file to a browser-shaped one. There is no query interface and no list of changes. You take the whole registry every time and work out what changed yourself.

FAA document search has no API at all. The Dynamic Regulatory System at https://drs.faa.gov holds the STC and airworthiness document set, and the page builds itself in the browser. On 13 August 2026 the STC browse view returned HTTP 200 with 22,793 bytes of markup and zero records in it. Every /api/ path we tried returned HTTP 403, and /drs-services/ paths returned the same 22,793-byte shell. Reading FAA STC records on a schedule means driving that page with an automated browser and parsing what it draws. That is a build, and it breaks whenever the front end of the site changes.

The EASA STC list is described as weekly and was nine months old. https://www.easa.europa.eu/download/stc/STC_WebList.pdf is a 12,846,196-byte PDF covering every EASA STC issued since 3 June 2004. On 13 August 2026 it returned Last-Modified: Wed, 12 Nov 2025 21:12:01 GMT. EASA says the list is updated weekly. The file's own date says otherwise, and the file wins. It is a good reference for who holds which design approval. We do not build alerts on it.

The two most aerospace-specific sources, FAA and EASA design approvals, are the two hardest to reach, and the generic federal sources are easy. That is unlikely to change.

The failures get rechecked as carefully as the successes. A source that quietly starts returning nothing is the most expensive failure in this work, because it does not look like a failure. It looks like a quiet market.

The source we deliberately do not use

Executive appointments are among the most valuable events in this work, and LinkedIn is the obvious place to get them.

We do not collect from it. Its user agreement prohibits using "software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services, including profiles and other data from the Services". The substitutes are the trade-press people-moves columns, company newsroom announcements, press-wire releases, SEC filings for the companies that file them, and a person reading an interface the way it is meant to be read. An appointment that can only be evidenced by a LinkedIn profile is recorded as unverified and does not enter the list.

What happens after the note

Before any note is sent, it goes through an export-control review: the sources it relies on, the recipient's jurisdiction, and a named person's recorded approval, all on file before anything leaves - the full procedure is published at export-control screening. Every reply is answered by a person, and a sequence stops the moment anyone responds.

Run this against your own market

Anyone can name the Federal Register. The hard part is the discipline: deleting the row with no source on the day the list is thin, checking the excerpt again before it is used, and putting every note through review before it sends.

If your company is on our top band, we read the public record every week for the accounts you name and send you what happened at each, with the source on every row. We send nothing on your behalf; what you do with it is yours.

Send us a link to something your company has published → /record/submit

What a channel is, and what it costs → /publish

• The review every note passes before it sends → /export-control-screening

Sources

Every claim on this page with its URL, its retrieval date and a recheck date. A claim that cannot be rechecked by its recheck date comes off the page.