Skip to content
Field NoteUAMAugust 26, 2026 · 4 min read

The 90-Second Turnaround Fallacy: Map the UAM Ground Handoff

A realistic turnaround model follows people, energy, inspection, baggage, data, and authority instead of assuming a single clock.

A fast aircraft can inherit a slow ground system.

Turnaround claims are often expressed as one clean number. In practice, several clocks run at once: passengers or payload must move, the vehicle must be inspected, energy must be replenished or exchanged, the next mission must be loaded, and an authorized person must release the movement. The slowest constrained path sets the real cadence.

The right planning tool is a handoff map. Each task receives a start condition, owner, resource, evidence output, and exception path. Parallel tasks should be distinguished from sequential ones. A task that usually takes thirty seconds may dominate reliability if it fails unpredictably and has no spare resource.

The 90-Second Turnaround Fallacy: Map the UAM Ground Handoff — editorial decision-flow infographic

Editorial infographic: Task map → Constraint → Exception → Real cadence. The diagram is a planning aid, not a certification or regulatory determination.

A four-part decision lens

  1. List tasks and start conditions. Make the condition visible in the same record used for the decision.
  2. Mark parallel and sequential work. Assign an owner and state what evidence will count as completion.
  3. Attach owner and scarce resource. Keep assumptions separate from observed or approved facts.
  4. Model exception and recovery time. Test the exception path, not only the preferred operating case.
  5. Measure the full distribution, not the best run. Review whether the control changed the next real decision.

What this looks like in the field

A demonstration achieves an impressive turnaround with one vehicle, a prepared crew, empty baggage, and a reserved charger. The service schedule later fails because passengers arrive unevenly and a single inspection discrepancy blocks the stand. The demonstration measured choreography; the operation must measure variability.

The management value lies in the boundary between one state and the next. A team must be able to see why an item moved from observation to action, from action to restriction, or from restriction to closure. If the transition has no named authority and no retained basis, the label is only decoration.

Governance before automation

Publish capacity as a range tied to assumptions. Include the median, the tail, and the recovery rule. If the model excludes accessibility needs, security checks, battery temperature, maintenance findings, or weather holds, label those exclusions before the number reaches investors or public planners.

Begin automation with an exception map rather than a feature list. Identify what may proceed normally, what requires review, what must stop, and which person can release it. Software can then surface deadlines and missing evidence without pretending to make the consequential judgment.

The practical test

Select a closed case and remove the people who remember it from the review. Ask a new reader to reproduce the sequence and identify the closure evidence. Any answer that begins with “I think” identifies a field, timestamp, or approval trail that the process failed to preserve.

Put it to work this week

Choose the most recent exception in this topic. Write its starting condition, decision clock, owner, evidence requirement, and closure rule on one page. Test the page with a second person and change the one line that creates the longest argument.

For this topic, use “List tasks and start conditions” as the opening prompt and “Measure the full distribution, not the best run” as the closure check. Keep both the original and revised record so the team can see whether the intervention reduced ambiguity rather than merely changing vocabulary.

The point is not to make turnaround look slow. It is to show which handoff deserves investment before a glossy target becomes a brittle schedule.

For the wider workflow, see the related UAM field note and the UAM KoreaTech books and workbooks.

Source and scope note

This column adapts a decision framework from the UAM, vertiport, and low-altitude operations book series. It is educational and vendor-neutral. It does not replace site-specific safety assessment, procurement law, aviation authorization, technical instructions, or professional advice. Useful primary starting points include:

Tags
UAM turnaroundvertiport capacityground handlingadvanced air mobility
More in UAM
Reviewed insight feed

Follow evidence-reviewed field notes.

Subscribe to the RSS feed for reviewed articles on drone operations, bird-strike risk, CBRN readiness, and aerospace ESG. We do not collect an email address until a verified mailing service is available.