Airffic Architect

World Innovation · Airffic

Size the aircraft. Screen the corridor. Export the simulation.

A workspace for multirotor engineers. Open it, run the bundled inspection quad, and read thrust, endurance, and airspace hits from the Architect engine.

Open the workspace Connect Claude, Grok, or ChatGPT
01Size

Quad, hex, or octo. Thrust-to-weight, hover, and range from the catalog you pick.

02Screen

Corridor, Japan checklist, 4D overlap, and a well-clear encounter. Advisory only.

03Export

PX4 parameters and a Gazebo bundle. Writing files asks you to confirm. Nothing arms.

Corridor

Check a route on the sample map, or on census DID, airport footprints, and elevation.

Same API

The page, REST, and MCP call one engine, so an assistant cannot invent a second set of numbers.

Bundled inspection quad

A sample airframe for jobs such as close-range bridge inspection under the deck (Airffic Inspection). 18-inch propellers, 6S 22 Ah, 1.5 kg payload, 3 m/s headwind. The engine’s coefficient model currently reports the figures on the right. They are not a thrust-stand measurement.

Sign-in is optional. A design stays in this browser until you create an account. Assistants use the same operations through MCP or OpenAPI.

Thrust / weight2.45
Hover22.5 min
Range14.4 km

Regulatory output is advisory. It is not an MLIT, DIPS, or certified-USP determination. Airport footprints are two-dimensional. The sample Kanto layer is unofficial. run_sitl_mission writes files and does not start PX4.