Product · Aeronautical Charts · Coming soon

Your own terminal charts, from your own navigation database.

Think of it as an in-house answer to Jeppesen and Navigraph. NavCharts draws SID, STAR, approach and enroute charts straight from ARINC 424 data — SVG and PDF, on your AIRAC cycle, with terrain from real elevation data. Built so an operator stops depending on somebody else's release schedule to get a chart changed.

SIDSTARIACEnroute ARINC 424SVG + PDFSRTM terrainAIRAC cycle

The chart set

Four chart types, at four levels of maturity.

We would rather tell you exactly where each one stands than sell you a finished product that is not.

SID

Departures

The complete implementation. Departure track geometry per physical runway, climb gradient table by ground speed, initial climb text, altitude and speed constraint symbology, MSA circle and terrain.

STAR

Arrivals

Plan view, info box, MSA and terrain in place, including not-to-scale inset boxes for distant transition fixes. Still being finished.

IAC

Approach

Plan view, profile view and header implemented. The landing minimums table is not — that data is not in ARINC 424 and needs a separate source.

ENR

Enroute

High and low enroute charts at a basic level, on A3 landscape.

Screenshotimg/shot-navcharts-sid.jpg
Generated SID chart

Departure charts

The geometry is computed, not traced.

Nothing on the departure page is drawn by hand. Every line comes out of the coded procedure.

  • One track per physical runway. The departure runways are read from the course of the CA/VA leg; 35L and 35R get their own track, each with its straight climb segment, its turn arc computed as a tangent from an external point, and the run out to the first fix.
  • Climb gradient table. FT/NM derived from the geometry — altitude gain over horizontal distance, with the CA leg length computed from ground speed and climb rate — then converted to FT/MIN across the standard 75 to 300 kt columns.
  • Constraint symbology to ICAO convention — bars over and under altitudes, speed restrictions in magenta with the bar below.
  • MSA circle, sectorised or full, with the reference fix chosen navaid-first and the radius honestly labelled when it has to be drawn out of scale.
  • Labels that do not collide. Heading and bearing/distance annotations run parallel to their track and are pushed apart iteratively until nothing overlaps.
Screenshotimg/shot-navcharts-terrain.jpg
Terrain overlay on a SID

Terrain

The high ground, on the chart.

Terrain is generated locally from SRTM elevation tiles — contour fill, raster fill and elevation labels — not fetched from a tile service at render time.

  • Contours pre-generated at 500 ft intervals and clipped to the plan frame.
  • Brown-tone relief palette in the convention pilots already read.
  • Optional per chart: on where terrain is the story, off where it is noise.

Data and output

Your database, your cycle, your file.

The database is yours

NavCharts reads standard ARINC 424 navigation databases and switches between them at runtime, without a restart. Navigraph and FAA CIFP cycles both work. The charts follow whichever cycle you are operating on.

SVG and PDF

Every chart is an SVG first, so it stays sharp and can be edited. The PDF is written from that same geometry at true 1:1 — and the page is sized to the procedure rather than the procedure squeezed into a fixed page.

Symbols from the source

Eighty vector symbols — navaids, waypoints, approach, obstacles, airports, airspace — drawn to the FAA Aeronautical Chart Users' Guide rather than approximated.

Where this is honest about itself. NavCharts is in development and not yet a commercial release. Departure charts are complete; arrivals, approaches and enroute are at the levels described above, and approach minimums are not available yet because that data does not exist in ARINC 424. If charts matter to your operation, talk to us now — the order the remaining work gets done in is still open.

At a glance

Specifications

Send us an airport and a procedure.

We will generate the chart from a current cycle and send you the PDF. It is the fastest way to see whether the output holds up next to what you use today.