Skip to content

A safety case the TAA can sign

The MAA does not want a folder of reports. It wants an argument that this air system is acceptably safe, and the evidence underneath it. CertProve builds both from your programme

What this regime costs you today

Each article is reissued on its own clock. Cite one without its issue and you are quoting text that moved.

The regulation moves under you

Every Regulatory Article is reissued on its own timetable. Your last submission may already quote text that has changed.

A folder is not a case

Reports prove things. Somebody still has to argue why the whole air system is acceptably safe, and defend it.

The hazard log outlives the team

It is read years later by people who were not in the room when the risk was accepted.

Two authorities, one aircraft

The design side recommends and the TAA releases. Each wants a different document, built from the same truth.

Whatever you fly, it has to be proven

The MRP reaches every UK military air system, and what it carries

  • Combat air
  • Air transport
  • Air to air refuelling
  • Airborne surveillance
  • Attack helicopter
  • Maritime helicopter
  • Support helicopter
  • Remotely piloted
  • Small uncrewed
  • Weapons and stores

What changes when the evidence derives itself

Cite what is in force

Every article is named at the issue it is on, read from the file the MAA publishes.

Argue it, do not just file it

The safety argument is a structured claim, and an unsupported branch is shown as unsupported.

Keep the log readable

Hazards, their acceptance and who accepted them, held together rather than scattered.

Produce both documents

The certificate of design and the release to service recommendation, from one set of evidence.

What we stand on, and what we will never do

what we stand on
The MRP Part 21 subparts with the MAA article named beside each one.
The article for every subpart read at the issue in force from the page the MAA publishes it on.
Design safety targets and cyber the articles that set what acceptably safe has to mean for your type.
Your own programme the certificate of design and the recommendation derive from your data, not a template.
what we will never do
Release anything the TAA releases. We build the recommendation and sign nothing.
Quote what we cannot read Def Stan 00-970 sits behind a login, so no basis is proposed from it.
Cite an article loosely an article without its issue is refused outright, because you cannot tell what was read.
Move your data single tenant inside your own boundary, markings on every export.
Check us on itPick an air system and read every record this composes, set-asides and all

Bring a change you have already been through

Bring a change you have already been through. Six weeks, against the articles your project is regulated by, at the issues in force

your own baselinesix weeksevery engineyou keep the report either way