Aircraft entry into service, rehearsed step by step before the first revenue flight
Each new aircraft type flies its first revenue flight on the date, with no day-one gaps.
See one case, screen by screen ↓Aircraft entry into service (EIS) is the work of readying a new aircraft type, or a new tail, for its first revenue flight: the maintenance program and ADs, manuals and OpSpecs, proving tests, trained crews, spares at every station and ground equipment. It covers both new aircraft type introduction and the induction of more aircraft of a type already in the fleet. Aircraft Entry into Service gives that work to seven agents that prove every readiness check with evidence and rehearse the first revenue flight step by step. The VP Technical Operations approves the fixes and signs each gate.
How to choose AI for airlines: a buyer's guide to agentic AI solutions →
Updated
Aircraft entry into service, or EIS, is the point where hundreds of things owned by a dozen departments have to be true on the morning of a new aircraft type's first revenue flight. The maintenance program is loaded and every AD accounted for. Manuals and the MEL are approved and on the pilots' tablets. The OpSpecs are amended and the proving tests flown. Pilots, cabin crews, dispatchers and mechanics are trained. Spares are in place at every station the aircraft touches, and the far end has ground equipment that fits, a handler and a line mechanic who know the type.
Today an EIS project office runs EIS preparation from a spreadsheet, and each owner marks their own row green. Nobody checks the record behind the green. Gaps surface at proving tests, at the gate or at the first outstation AOG. And a schedule change quietly breaks plans nobody re-checks: when network planning moves the launch route, the pool agreement, the station list, the ETOPS alternates and the crews' route training all have to follow.
Estimated split for one week of an EIS program office on a new widebody type, by hand and with the solution.
Seven agents prove every readiness check, rehearse the first revenue flight step by step, and draft the fix where it would fail; technical operations signs off.
Corvane Airways' first A350-900 revenue flight is CV 30 from Denver to Tokyo Narita on Friday, May 14, 2027, on N351CV. Today is October 15, 2026. This is how aircraft entry into service runs in the working solution, screen by screen: the agents rehearse the flight, find what would stop it, and the VP Technical Operations decides.
Dana's morning starts with four numbers: 211 days to CV 30, 362 of 412 readiness checks ready, 6 at risk with 1 that stops the first flight, and gate 3 in 32 days with 8 of 9 criteria met. Four items need her, at the top a pool request for spares at NRT. Below is what the agents did overnight, and the readiness agent's briefing, which she can ask questions of in plain words.
Briefing: “Last night's rehearsal stopped at spares at NRT: 14 rotables are in no pool there. The spares agent drafted the fix and it needs you by Dec 15.”
The readiness agent walked CV 30 through its 14 moments, from crew sign-in at 09:05 to the records after arrival. Each moment reads its records: two captains and two first officers typed and current, OpSpec B342 for ETOPS in FAA review on Nov 19, performance data for N351CV, ETOPS alternates ANC and CTS. Eleven were ready and two on plan. It stopped at step 12, spares at NRT.
“CV 30 would not fly as planned today: 11 ready, 2 on plan, 1 not ready.”
The NRT station kit lists 41 parts, and 27 are covered by initial provisioning, shipping to the NRT bonded store by Apr 20. The other 14 rotables are in no pool there: pool agreement PA-2024-118 covers DEN, SEA and LHR. It was signed for the London launch. Schedule change SC-0412 moved the launch to Narita on Aug 27, and Materials was not on its distribution. The check agent read the same sources blind and got the same result.
“If CV 30 landed at NRT and a rotable failed on the turn, there would be no spare at NRT, and CV 31 back to DEN would cancel.”
The spares agent priced three ways to cover NRT. A: add NRT to the pool for $14,200 a month, $170,400 a year, with about $22,540 of exchanges, stocked by Apr 14 if requested by Dec 15. B: buy and stock the 14 rotables for $3,862,000 of capital. C: fly parts in from DEN, about $1.1M of exposure with each event canceling CV 31. The check agent recomputed option A blind, at $170,400 a year and 2.30 expected removals, and agrees at confidence 0.93.
“I recommend A: about $192,940 in year one against $3.86M to buy, and no canceled CV 31 when a part fails at NRT.”
New recurring spend over $100,000 a year needs the VP Technical Operations, so the drafted pool request PR-0907 waits for Dana. She picks reason code A1, recommended option, lowest risk, and signs. Only then is the request sent to Altamesa Component Services with her signature. She could have edited the draft, asked for a lower access fee, or rejected it with a reason.
“I approve PR-0907 and its send to Altamesa as Dana Whitfield, VP Technical Operations — e-signature.”
The rehearsal runs again from the systems of record: 11 ready, 3 on plan, 0 not ready. Spares at NRT is on plan, with the 14 rotables at NRT by Apr 14, 2027 and Teresa Alvarez as owner. Readiness check SP-041 moves to on plan, and gate 3's criterion 6, a spares plan for every first-route station, is met.
“12 · Spares at NRT — on plan: Pool request PR-0907 approved; the 14 rotables are at NRT by Apr 14, 2027.”
A check counts as ready only when its record proves it and the check agent agrees. On RA-031, the APU back-to-birth sheets for N352CV, the owner marked it ready and the maintenance program agent read 46 sheets in the delivery records index. The check agent read the sheets themselves and found 2 missing, for the turbine wheel and the compressor impeller. The check stays at risk and blocks gate 4 until both readings agree, and the owner has the action to get the 2 sheets from the manufacturer by Nov 30.
“The agents disagree, so this check is not ready.”
The maintenance program agent mapped 2,890 of the manufacturer's 2,914 planning tasks into Corvane's program, by ATA chapter, and lists the 24 task cards still to write by Jan 29. It read AD applicability for MSN 6412: 41 of 41 ADs accounted for, 3 of them recurring in the program. Lena's reliability alert levels for ATA 21, 29 and 36 are overdue, and the agents escalated them.
OpSpec A003 for the A350-900 was approved Aug 14, 2026. B342, the ETOPS approval for the A350-900 up to 180 minutes over the North Pacific under Appendix P to Part 121, is in FAA review on Nov 19, and D095, MEL revision 0, on Dec 3. D085 adds each tail the day after delivery. The proving test plan under 14 CFR 121.163(b) is 50.5 hours, Apr 14 to May 4, 2027, at NRT, ANC and SEA. The agent drafts the B342 package; a person submits it.
Asked whether the FAA paperwork is on the critical path: “No, by 5 months.”
Gate 3 now shows all 9 criteria met, from the maintenance program revision submitted to the FAA to a first revenue flight rehearsed in the last 7 days, each with its source. The readiness agent says the gate is ready for her signature. She can sign or hold it with a reason, and export the evidence pack for the FAA principal inspectors.
“All 9 criteria are met with evidence. The check agent re-read each one.”
The same entry into service, seen by the five people who carry it: what their program looked like, and what it looks like now.
Seven agents prove every readiness check, rehearse the first revenue flight step by step, and draft the fix where it would fail; technical operations signs off.
Owns the program: re-checks every readiness check nightly, rehearses the first flights step by step, writes what is at risk, assigns owner actions and escalates.
Maps the manufacturer's planning document into the maintenance program, reads AD applicability per MSN and proposes reliability alert levels.
Tracks OpSpec amendments and FAA milestones, compares manual revisions with the manufacturer's, checks the loads on the pilots' tablets and drafts FAA packages.
Compares recommended spares with what is covered at every station, prices the options and drafts pool requests and orders.
Reads training records and matches trained pilots, cabin crews, dispatchers and mechanics to the schedule. It proposes simulator swaps, and when asked for another option it finds one, prices it and says which it still recommends.
Checks ground equipment fit, handler training, line maintenance contracts and alternates at every station the type touches.
Re-verifies every ready check and every priced option blind from the raw records.
Approves spend over $100,000 a year and signs every readiness gate. The agents propose; a named person decides.
Ask about any step, check or gate, or tell the agents what to do. Answers cite their source; nothing is approved, sent or signed until a person says so.
Would CV 30 fly today?
Not as planned: 11 of 14 steps are ready and 2 are on plan, but spares at NRT is not ready — 14 rotables are in no pool there.
Why didn't the pool follow the route change?
SC-0412 went to Network Planning, Flight Operations, Inflight and Airport Operations — not to Materials. The pool agreement still lists DEN, SEA and LHR. I have added Materials to the distribution rule for schedule changes that touch a new station; that change waits for the administrator in Settings.
How do you know a check is ready?
Each check reads its record in the system of record: a task card, a training record, a contract, a photo. I read the same record without seeing the first answer. Only when both agree, at confidence 0.85 or more, does it count as ready. Self-reported status never counts.
Is the FAA paperwork on the critical path?
No, by 5 months. The latest item before the flight is the proving tests, Apr 14 – May 4. ETOPS B342 is reviewed Nov 19 and the MEL Dec 3.
Who approved PR-0907?
Dana Whitfield, Oct 15, 2026 07:43: approved pool request PR-0907, adding NRT to PA-2024-118 for 14 rotables at $170,400 a year, reason A1. The entry is chained to the one before it, so it cannot change unseen.
13 screens from the working solution, on its sample data. Pick one to see it large.
The rules every readiness check and decision runs on are settings, and every change waits for a second signer.
| Setting | Default | Choose from |
|---|---|---|
| Spend that needs the VP Technical Operations | $100,000 a year | Any amount of new recurring spend per year; a change waits for a second signer |
| Check agent must agree | On | On · Off — a check counts as ready only when both readings agree |
| Confidence floor | 0.85 | Below it, the agent asks a person instead of answering |
| Nightly re-check | 02:00 MT | Any time; all 412 checks read again from the systems of record |
| Rehearse after every schedule change | On | On · Off — first flights rehearsed again the night a change is issued |
| Default due date for owner actions | 10 business days | Business days from when the agent asks |
| Reminders before the due date | 5 and 2 days | Sent by the readiness agent with the evidence needed |
| Escalate overdue actions | On | To the domain head after 1 day, to the VP after 5 |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample program data · “estimated” = our estimate ($411,000 a day = 306 seats × 84% load × $800 average one-way fare × 2 sectors on DEN–NRT; the hours in “where the week goes”) · “typical” = published figures (Oliver Wyman, record 17,000-aircraft order backlog, 2025; 14 CFR 121.163 on proving tests; 14 CFR 121.367 on maintenance programs; 14 CFR Part 121 Appendix P on ETOPS). People, Corvane Airways, Altamesa Component Services, N351CV, N352CV and PR-0907 named on this page are fictional: characters and sample data in the working solution.
Aircraft entry into service (EIS) is the work of readying a new aircraft type, or a new tail, for its first revenue flight: the maintenance program and ADs, manuals and OpSpecs, proving tests, trained crews, spares at every station and ground equipment. It covers both new aircraft type introduction and the induction of more aircraft of a type already in the fleet. Aircraft Entry into Service gives that work to seven agents that prove every readiness check with evidence and rehearse the first revenue flight step by step. The VP Technical Operations approves the fixes and signs each gate.
In the working solution, 412 readiness checks in 8 domains: maintenance program (required under 14 CFR 121.367), records and ADs, manuals and OpSpecs, spares and pools, flight crews, cabin crews, stations and ground equipment, and systems and data. The rehearsal walks the first flight's 14 moments, from crew sign-in to the records after arrival, and says at each one whether it is ready, with the evidence.
Under 14 CFR 121.163, an airplane type not yet proven in Part 121 service needs at least 100 hours of proving tests, and an operator flying a type in a kind of operation it has not proven before needs at least 50 hours for each kind of operation, including a representative number of flights into en route airports. In the demo, the proving test plan is 50.5 hours, Apr 14 to May 4, 2027. The manuals and OpSpecs agent tracks it with the OpSpec amendments and other FAA milestones.
The agents read every schedule change from network planning, re-plan the readiness checks and rehearse the first flights again that night. In the demo, schedule change SC-0412 moved the launch from London to Tokyo, and the rehearsal found that the component pool agreement never followed: 14 rotables were in no pool at NRT.
The spares agent compares the recommended spares with what is covered at every station: initial provisioning, station kits and pool agreements. Where a station is short it prices the options and drafts the request. At NRT it priced adding the station to the pool at $170,400 a year, buying the 14 rotables at $3,862,000, or flying parts in from DEN.
No. A check counts as ready only when its record proves it and the check agent, reading blind, agrees. The agents draft pool requests, FAA packages and simulator swaps, but never commit money, sign an agreement, submit to the FAA, book a slot or sign a gate.
Yes. Every decision is a person's, with a reason code and an e-signature: spend over $100,000 a year goes to the VP Technical Operations, and she signs or holds each gate on cited criteria. Station managers confirm their stations with their own evidence, rule changes need a second signer, and every action is on a chained audit trail.
Yes. The working solution runs every program in one place: the A350-900 new type, an A321XLR new variant, 787-9 tail inductions of an existing type, and the integration of an acquired airline's 22 A220-300s. A new program starts from the type, the first revenue flight and the stations, and the agents load the readiness checks and propose owners. In the demo, the 787-9 tail inductions run on 96 readiness checks, against 412 for the new A350-900 type.
The Agentic Solution Engine builds and deploys it from your requirements and documents, such as your EIS plan, readiness checklists and systems of record, and it goes live once every quality gate has passed. We will walk you through it on your own next type or induction first.
Every lease return handed back on its date, inside budget, with every gap priced.
1-min demoAircraft Technical Records AuditEvery records gap found a year before handback, each with the page the agent checked.
1-min demoAircraft Lease ManagementEvery lease obligation tracked to its clause, so nothing surfaces first at lease end.
1-min demoWe'll rehearse the first revenue flight of your next aircraft type or tail induction with Aircraft Entry into Service.