THE MISSION,
LEG BY LEG.

Know the aircraft. Know who holds the stick. Read the condition it is in today.

Nobody flies an aircraft they cannot identify, and nobody should fly one whose controls somebody else is holding. This leg settles both before a single number is declared: what you are made of, whose hand has been on the throttle, and the as-found condition of the structure right now — measured, not remembered. The program is emphatic here: Task 0. Always. Never Task I. Declare a service life with captured authority and you will faithfully declare somebody else's, and every task above it will be executed rigorously against the wrong requirement.

• Name your material — take the Mind My Material assessment and read the sheet without flinching — brittle, ductile, tough, and what that costs.
• Trace your command authority — walk your load history and write down who has been assigning the loads. If the answer is not you, that is the first finding.
• Open the logbook — one number a night in Hindsight Daily. The baseline is the first thing every later gauge is read against.

Declare the mission in numbers: how long, in what mix, to what criteria.

A brief is not a wish. It states the service life you intend to fly, the mission mix by the hour, the horizon to recertification, and the criteria the structure will be held to. The governor is set here — the fixed end conditions that decide how much load you can carry before you buckle — and the joints are inventoried, because a structure fails at its connections before it fails in the skin. Converge first: narrow to the mission that carries thrust, then let it open.

• Declare a service life — hours per week per mission element, a start date, a recertification date. Written down, it can be held to a Tuesday.
• Set the governor — name the end conditions that fix your buckling load — the people, clocks and rules that stop you — and make them external.
• Inventory the joints — list every connection the structure hangs on, with its allowable. The joint register is read again at every inspection.

Put the loads on paper, then run the fatigue math on your own record.

Before the test flight, the planning: a free body diagram of the life you are flying — lift, weight, thrust, drag, the headwind — and the spectrum of cycles those loads produce. Then the analysis the whole program rests on: durability and damage tolerance run on your logged days, which give a damage curve and, from it, an inspection interval that is yours rather than a calendar's. Coupon tests are designed here too — small, declared experiments on one practice — and the economic service life gets a price.

• Draw your free body diagram — every force on the airframe, named and pointed. If you cannot draw it, you cannot size it.
• Read a load spectrum — where the cycles come from, how big, how often — damage lives in the swings, not the altitude.
• Run the fatigue analysis — rainflow, Walker, Miner on your own days: a damage number, a rate, an inspection interval.
• Design a coupon test — one practice, ON days and OFF days, a falsifier written before the run.

Instrument the airframe and fly the card. Log what it actually does.

Analysis predicts; the test verifies. The ring-down test taps the structure and times how fast it settles back to its set point — the Modal Survey, a sub-task of pre-flight verification. The flight test flies the predicted mission against the record and reads the difference. Everything that turns up is a finding: numbered, dated, open or closed, in a register that follows the airframe for the rest of its life.

• Run the ring-down — how many days to return to set point after a jolt, and whether the set point moved.
• Fly a test card — predict the number first, then fly, then compare. The gap is the lesson.
• Keep a findings register — a finding is not a failure; it is a dated line with a disposition. Close them or carry them, never lose them.

Everything converges to four sheets. Then it opens.

The pinch in a nozzle is not damage; it is the precondition for thrust. All the analysis and testing compresses here into four artifacts you can hold: a certification basis (what this structure is cleared to fly, to what limits), a placard set written in plain words, a one-page maintenance plan, and a repair manual of the fixes certified to work on you. Placards price exceedance rather than forbid it — a Form A-1 authorizes the excursion, with its expiry written on it — because integrity is the paperwork matching the flight.

• Write placards in plain words — a limit you cannot read at a glance is not a limit. Seven is plenty.
• Price an exceedance — file the A-1 before the excursion, with an abort rule written against a clock, a place, or a named person — never a feeling you would have to notice.
• Write the one-page maintenance plan — what gets inspected, how often, by whom. The 𝑖SMP is the sheet the whole year is flown from.

Log, track, inspect at the interval, repair, recertify. Then pass it on.

A program without Task V is a binder on a shelf. This is the daily and weekly rhythm: one number a night; the week painted as flown against the week declared; the damage read when the inspection comes due and not before, because a gauge watched continuously starts flying the aircraft; a deep audit on the long interval; repairs tagged, tested and certified; and recertification when the mission changes — which sends you back to the brief, this time with data. The last task is the transfer of the method to somebody else.

• Hold the nightly number — ten seconds, every night, for years. The instrument is only as good as the record.
• Read at the interval — look at the gauges when the inspection is due, not every day. Over-monitoring couples you to the thing you are measuring.
• Tag and test repairs — name what you tried, run the coupon, certify what held, ground what did not.
• Recertify on mission change — a new mission is a new brief. Go back to Leg 1 carrying the record.
• Transfer the method — Objective 5 — teach it, write it, show someone else the map.