How do I install the Flight Planning skill?

Run npx skillmds@latest add ashfordeou/flight-planning in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Flight Planning safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Flight Planning?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Flight Planning free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Flight Planning?

ashfordeOU (@ashfordeou) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Flight Planning by ashfordeou — Agent Skill

Name: Flight Planning
Author: ashfordeOU

Flight Planning

Use when you must build and check a flight management system flight plan: compute great-circle leg distances between waypoints, verify the vertical profile against crossing constraints, and total the track distance for fuel and time planning. Produces the leg distance check, the vertical constraint verdict, and the flight plan validity flag that gates dispatch planning. Trigger: flight planning, flight management system, waypoints, vertical profile, track distance, fms.

ashfordeOU bf003a9 3 files · 7.7 KB Updated Sep 17, 2026

File contents

FMS Flight Planning (avionics/flight-management/flight-planning)

Use when the task is flight management system flight planning: waypoint geometry, vertical profile constraint checks, and track distance accounting for a planned route.

Domain quick reference

A flight plan is a sequence of waypoints and the legs between them; each leg has a great-circle distance.
The vertical profile must satisfy crossing constraints: floor and ceiling altitudes at waypoints.
Track distance drives fuel and time planning.
A flight management system executes the plan under the airborne software lifecycle discipline of DO-178C.

Workflow

Collect the waypoint sequence with coordinates.
Compute each leg distance with leg_distance_km.
Check the planned altitude against every crossing constraint with vertical_constraint_ok.
Total the track with total_distance_km.
Gate the plan with flight_plan_ok.

Pitfalls

Using flat-earth distances on long oceanic legs.
Ignoring a floor constraint when cleared higher.
Planning altitude against the wrong constraint pair.

Behavior contract (gate 3)

The leg-distance, constraint, and validity logic is exercised by the gate 3 contract test: scripts/test_flight_planning.py against scripts/flight_planning_logic.py (stdlib unittest, offline). Run: python3 scripts/test_flight_planning.py

Compliance

Standards referenced, not reproduced: DO-178C text is proprietary (RTCA); the flight planning process here is common methodology, summary-only per standards-map.yaml and brief 06.
compliance: STANDARDS-REF, gated: false.

---name: flight-planningdescription: Use when you must build and check a flight management system flight plan: compute great-circle leg distances between waypoints, verify the vertical profile against crossing constraints, and total the track distance for fuel and time planning. Produces the leg distance check, the vertical constraint verdict, and the flight plan validity flag that gates dispatch planning. Trigger: flight planning, flight management system, waypoints, vertical profile, track distance, fms.license: Apache-2.0---# FMS Flight Planning (avionics/flight-management/flight-planning)Use when the task is flight management system flight planning:waypoint geometry, vertical profile constraint checks, and trackdistance accounting for a planned route.## Domain quick reference- A flight plan is a sequence of waypoints and the legs between them; each leg has a great-circle distance.- The vertical profile must satisfy crossing constraints: floor and ceiling altitudes at waypoints.- Track distance drives fuel and time planning.- A flight management system executes the plan under the airborne software lifecycle discipline of DO-178C.## Workflow1. Collect the waypoint sequence with coordinates.2. Compute each leg distance with leg_distance_km.3. Check the planned altitude against every crossing constraint with vertical_constraint_ok.4. Total the track with total_distance_km.5. Gate the plan with flight_plan_ok.## Pitfalls- Using flat-earth distances on long oceanic legs.- Ignoring a floor constraint when cleared higher.- Planning altitude against the wrong constraint pair.## Behavior contract (gate 3)The leg-distance, constraint, and validity logic is exercised by thegate 3 contract test: scripts/test_flight_planning.py againstscripts/flight_planning_logic.py (stdlib unittest, offline). Run:python3 scripts/test_flight_planning.py## Compliance- Standards referenced, not reproduced: DO-178C text is proprietary (RTCA); the flight planning process here is common methodology, summary-only per standards-map.yaml and brief 06.- compliance: STANDARDS-REF, gated: false.

Frequently asked questions