Tarmac delay rule compliance that starts every return to the gate in time and drafts the DOT report the same day
Every return to the gate started in time, and every DOT report ready the same day.
See one case, screen by screen ↓Tarmac Delay Compliance is tarmac delay rule compliance for airline operations control: agents watch every aircraft holding with passengers against the 3-hour domestic and 4-hour international limits of 14 CFR 259.4, predict each breach from the deice queue and ATC programs, and give the duty manager a start-back-by minute and a named gate. They log food and water and status updates against the contingency plan, and after a long delay draft the DOT report and evidence pack for a compliance analyst to certify.
How to choose AI for airlines: a buyer's guide to agentic AI solutions →
Updated
Tarmac delay rule compliance starts on a storm day. Snow, a ground stop at the destination or a deice queue holds aircraft full of passengers on the ground, and under 14 CFR 259.4 the airline has three hours on a domestic flight, four on an international one, to give them the chance to get off. Food and water are due by two hours, lavatories must work, passengers hear a status update every 30 minutes, and the return to the gate has to begin before the limit. The OCC duty manager and the tarmac delay coordinator watch those clocks on a flight-movement screen and a whiteboard, judge from the deice queue and the ATC program whether a flight will lift off in time, and phone the station for a gate while the gates are full of arrivals waiting themselves.
Then comes lengthy tarmac delay reporting. Every delay over the limit at a US airport owes DOT a written report within 30 days, with cause, actions and a signed certification, and international and charter delays go on BTS Form 244. The compliance analyst rebuilds each event weeks later from ACARS, the gate system, the ramp log, the cabin crew report and ATC advisories — which disagree about when the door closed. The cost of getting it wrong is public: DOT fined one US network carrier $4.1 million for 43 domestic flights held more than three hours, and the cap is now $75,000 per violation.
Estimated split of the hours one long tarmac delay takes across ops control and compliance, by hand and with the solution.
Seven agents time every ground hold, plan the return and write the report; the duty manager decides every return.
Thursday, February 12, 2026, 15:15 CST. Snow at Chicago O'Hare, departures down to 18 an hour, a ground stop at Boston until 16:30. Corvane Airways has eight aircraft holding with passengers. Here is what happens next, screen by screen, in the working solution.
Teresa's Today screen leads with a single decision: CV 902 to Boston must start back to the gate by 15:40. Out since 13:05 with 186 passengers, it will not make it — Boston's ground stop puts takeoff at about 16:48, 43 minutes past the limit. Below it: 8 aircraft holding, 1,415 passengers at ORD, 5 gates freeing in the next hour, and 0 over the limit this winter.
Waiting for you: “Approve the CV 902 return to B14 — decide by 15:40 · 25 minutes.”
The hub's surface is one clean diagram — concourses B and C, deice pads 1 and 2, the Ramp 5 hold pad, the runways. Each aircraft sits in a ring that shows how much of its 3- or 4-hour limit is used: CV 902 at 2:10 of 3:00, CV 2210 at 2:17, CV 47 to London at 1:55 of 4:00. Tarmac Watch has already re-predicted the two Boston flights from ATC advisory 087 and flagged CV 1418 to DCA as at risk.
Return Planner, beside the ring: “Gate B14 frees at 15:20. Taxi back and door open take 25 minutes. Start back by 15:40, or we breach the 3-hour limit at 16:05.”
The CV 902 drawer shows why. The clock started at 13:05, when the main door closed and the aircraft pushed from B12. The limit is 16:05, 3 hours domestic. It is sixth in the deice pad 2 queue, food and water was served at 14:52 and four status updates have been made, the last at 15:05. Each line links to the ACARS message, gate record or advisory it came from.
Tarmac Watch never starts or stops a clock by assumption — every start time cites its source.
Return to B14: start back by 15:40, door open 15:44 at 2 h 39, 21 minutes inside, re-depart about 17:31 — recommended. Wait for deice and fly: predicted takeoff 16:48, 43 minutes over, exposure up to $75,000 a passenger. Deplane at the pad: 35 minutes to set up stairs and 2 buses, earliest 15:55, possible but slower and riskier in snow.
The Return Planner proposes; every return is the duty manager's call.
Teresa approves the return of CV 902 to B14 and picks the reason code — breach predicted, return before the limit. The decision, her name and the time go on the audit trail, and B14 is held for CV 902.
“You decide; the agents then draft the captain's ACARS and the station message for you to send.”
Two drafts appear in the conversation: the ACARS to Capt. Daniel Reyes — Boston ground stop until 16:30, predicted takeoff 16:48, 3-hour limit 16:05, return to gate B14, begin taxi back no later than 15:40 — and the message to Kristin Haugen at the station, asking for the tug, the jet bridge operator, two agents for rebooking and wheelchairs for 4C and 11A. Nothing goes until Teresa presses Send both.
“REQ BEGIN TAXI BACK NLT 1540. RAMP TWR EXPECTING YOU. PLS ACK -TV”
Capt. Reyes replies “WILCO RETURNING B14”. Kristin approves the gate hold, with the tug and jet bridge on B14 from 15:30. The return begins at 15:21 — Corvane controls the B ramp, so it begins when the captain starts maneuvering. Passengers are told they may get off at the gate, the aircraft is on B14 at 15:42 and the door opens at 15:44: 2 h 39 on the ground, 21 minutes inside the limit. 31 of the 186 passengers ask to get off, and agents at B14 rebook them.
Outcome: “Event closed with its evidence: every time is cited, the decision signed and logged.” No DOT report needed — under 3 hours.
For all eight aircraft, the passenger care grid shows status updates every 30 minutes, food and water by 2 hours, lavatories, medical help and the deplaning notice, each from a crew entry. CV 1418's purser started the service at 15:20; it is logged at 15:24, 1 h 52, inside 2 hours. On CV 1733 one passenger was helped with insulin timing.
The Passenger Care Logger never marks a duty done without a crew entry.
CV 1164 from Newark spent 3 h 23 on the ground on January 25 and is reportable. The Evidence Checker reconciled ten moments across five sources. The gate system says the main door closed at 14:11, ACARS says 14:12; it used 14:11, the conservative time. The exception — EWR tower advising at 16:54 that a return would significantly disrupt airport operations — is backed by three sources.
The Evidence Checker can block a draft, never approve one.
The Report Writer drafted the 30-day report to the Office of Aviation Consumer Protection 3 hours 36 minutes after takeoff, due February 24. Elaine sees 11 of 11 fields citing their source, the exception evidenced at the time and the plan followed — food and water at 1 h 49, updates on time. She ticks the certification under 14 CFR 259.4(g)(3) and presses Certify and file; the filing comes back with its receipt.
“I certify that the information in this report is accurate to the best of my knowledge.”
The same storm, seen by the five people who carry it — what a long tarmac delay looked like for them, and what it looks like now.
Seven agents time every ground hold, plan the return and write the report; the duty manager decides every return.
Runs every aircraft's clock from the earlier of the main door closing and OUT for departures, or touchdown for arrivals, and predicts takeoff and breach from the deice queue, holdover time, departure rate and ATC ground stops and programs — 3 hours domestic, 4 international.
Works back from the limit through gate release, taxi-back and door time to the latest minute a return can start, names the gate, and compares returning, waiting and remote deplaning.
Logs status updates, food and water, lavatories, medical help and deplaning notices from the cabin crew app and ACARS against the contingency plan, and drafts a nudge to the purser before a duty falls due.
Drafts the ACARS to captains and the messages to the station and ramp, and reads the replies back into the return plan.
Checks every action against the airline's Contingency Plan for Lengthy Tarmac Delays clause by clause, and tracks coordination with airport authorities, CBP and TSA, drafting renewal letters before they lapse.
Drafts the 30-day long-delay report under 14 CFR 259.4(g), BTS Form 244 when it applies, and the evidence pack, and watches every filing deadline.
Reconciles every timestamp across ACARS, the gate system, the ramp log, the cabin crew report and ATC advisories, takes the conservative time when they disagree, and blocks a draft until a mismatch is explained.
Approve each return, send each message, certify each report. The agents propose; a named person decides.
Ask the tarmac agents in plain words — or tell them what to do. Every answer points to the ACARS message, gate record, plan clause or rule it came from.
Why must CV 902 start back by 15:40?
Gate B14 frees at 15:20; taxi back from deice pad 2 takes 18 minutes and opening the door 7. Corvane's plan wants the door open before the 16:05 limit. Waiting means takeoff about 16:48, after Boston's ground stop and a second deicing.
Hold fallback gates for every flight at risk
Two aircraft need one: CV 902 → B14 from 15:20 and CV 1418 → B9 from 15:45. I sent both holds to Kristin Haugen at the station to approve.
Which aircraft still owe food and water in the next 30 minutes?
One: CV 1418 to DCA, due at 15:32 — the carts are only being set up. CV 902, CV 2210, CV 47 and CV 1733 are served, each before 2 hours. The rule is 2 hours from the start of the delay.
Is the CV 1164 report ready to certify?
Yes. All 11 fields cite their source; the Evidence Checker resolved one conflict — the door closed at 14:11 by the gate system, 14:12 by ACARS, and the earlier time is used, making it 3 h 23. The ATC exception is backed by three sources. Due February 24; it needs Elaine Brooks' signature.
13 screens from the working solution, on its sample data. Pick one to see it large.
The clocks, thresholds and rules the agents work to are settings, versioned and logged — the limits from 14 CFR 259.4, the rest from your own plan.
| Setting | Default | Choose from |
|---|---|---|
| Domestic and international limits | 3 hours · 4 hours | Locked by 14 CFR 259.4 — may only be made shorter |
| Clock start | Earlier of door closed (gate system) and OUT (ACARS) | On · off — the conservative Corvane rule |
| Start watching an aircraft at | 60 minutes | Any number of minutes |
| Plan a return from | 2:00 domestic · 3:00 international | Hours on the ground |
| Food and water reminder at | 1:45 | Any time · Corvane plan §3.1 |
| Status update every | 30 minutes | Any number of minutes · Corvane plan §3.3 |
| Airline target | Door open before the limit, not only the return begun | On · off — plan §2.1 |
| Propose remote deplaning when no gate frees in time | Off | On · off |
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 data · “target” = the design goal, measured in the live solution · “estimated” = our estimate ($95,000 per flight is our arithmetic on the published order) · “typical” = published figures (DOT Order 2023-8-20 — $4.1 million for 43 flights; 89 FR 106282 — $75,000 per violation; 14 CFR 259.4 and Part 244). People, airlines, flights and aircraft named on this page — Corvane Airways and Northline Connect among them — are fictional: characters and sample data in the working solution.
Tarmac Delay Compliance is tarmac delay rule compliance for airline operations control: agents watch every aircraft holding with passengers against the 3-hour domestic and 4-hour international limits of 14 CFR 259.4, predict each breach from the deice queue and ATC programs, and give the duty manager a start-back-by minute and a named gate. They log food and water and status updates against the contingency plan, and after a long delay draft the DOT report and evidence pack for a compliance analyst to certify.
The DOT tarmac delay rule, 14 CFR 259.4 — often called the three-hour tarmac rule — says an airline must begin to return an aircraft to a place where passengers can get off within 3 hours on a domestic flight and 4 hours on an international one, unless an exception applies. It also requires food and water by 2 hours, working lavatories, medical attention, status updates every 30 minutes and telling passengers whenever they can get off.
A delay over 3 hours domestic or 4 hours international at a US airport needs a written report to DOT's Office of Aviation Consumer Protection within 30 days, with a signed certification (14 CFR 259.4(g)). International and charter tarmac delays also go on BTS Form 244, the Part 244 tarmac delay report. The Report Writer drafts both and tracks each deadline; a compliance analyst certifies and files.
The tarmac delay exceptions are narrow. The pilot in command may determine that deplaning would jeopardize safety or security, or that the aircraft cannot leave its position for a safety or security reason, and ATC may advise that a return would significantly disrupt airport operations. In the solution the duty manager records the exception with its reason, and it needs a cited message from the captain or ATC, so the report rests on evidence captured at the time.
Tarmac Watch starts each clock at the earlier of the main door closing and OUT, then predicts takeoff from the deice queue, holdover time, departure rate and ATC ground stops and programs. The Return Planner works back from the limit through gate release, taxi-back and door times to the latest minute a return can start — for CV 902, start back by 15:40 for a 16:05 limit.
Yes. The Plan Conformance Checker reads the airline's Contingency Plan for Lengthy Tarmac Delays clause by clause and checks every action against it during the storm. It also tracks coordination with airport authorities, CBP and TSA at each airport and drafts renewal letters before they lapse; it never changes the plan.
Yes. Every return to the gate is the duty manager's call, with a reason code; ACARS and station messages are drafts until a person sends them; gate holds need the station operations manager; and only a regulatory compliance analyst certifies and files a DOT report. The agents never move an aircraft, declare an exception or file anything.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your contingency plan, station timings and a sample of past storm days from your ACARS, gate and cabin crew records — and it goes live once every quality gate has passed. We will walk you through it on one of your own storms first.
Every disability complaint answered within 30 days, with the facts rebuilt and cited.
1-min demoMishandled Wheelchair ReportingEvery damaged chair traced to where it happened, remedied the same day, and counted right.
1-min demoAirline Passenger Rights ComplianceEvery passenger's refund, care and compensation, planned before the gate improvises.
1-min demoWe'll replay Tarmac Delay Compliance on one of your own past storm days, from your ACARS, gate and cabin crew records.