Getting Your Navigation Data Right When Things Get Real
I spent about six years working flight planning for a regional operator that used a mix of Jeppesen and third-party manual sources. One thing I learned early on is that relying on a single data source for instrument approaches and terminal procedures is a fast way to get yourself into trouble. The Jeppesen Instrument Commercial Manual Nethflight Rexair reference comes up because some operators try to bridge the gap between official authority publications and commercial chart packages. It works in theory. It does not always work in practice. The term itself points to a combination of materials rather than one single published document. Jeppesen produces standard instrument approach plates, terminal area charts, and commercial route guidance. Nethflight has historically been a European flight planning service that aggregates and sometimes republishes approach data. Rexair appears in discussions as a smaller operator or charter company that relied on manual compilation methods rather than full electronic solution integration. When people reference the Jeppesen Instrument Commercial Manual Nethflight Rexair together, they are usually talking about a hybrid workflow where someone takes Jeppesen commercial manual data and cross-references it against manually compiled sources from smaller operators or independent chart publishers. This hybrid approach exists because not every airport in the world gets the same level of charting coverage from a single provider. Some regions have gaps. Some airfields have unpublished approaches or temporary procedures that do not make it into the standard Jeppene update cycle. That is where manual compilation comes in.
How the manual cross-referencing process actually works You take your Jeppesen manual for the region you are flying into. You open the approach plates for your destination and any alternates. Then you pull whatever supplementary material is available. This might include national AIP publications, NOTAM compilations, operator-specific supplements, and sometimes older charts from services like Nethflight that may have archived approach variations. You compare them side by side and look for discrepancies in minimums, published runway lengths, obstacle clearance altitudes, and frequency information. I used a physical desk setup for this. Two chart stands, highlighters in three colors, and a timing system where I would flag any approach where the Jeppesen minimums differed from the AIP by more than two hundred feet or where the runway threshold coordinates did not match. This process took roughly forty-five minutes per route for a typical domestic European flight plan. If you are flying an international route into a less-charted region, expect to spend around two hours on the manual cross-check before you even consider filing the flight.
The Problem Nobody Talks About
The biggest issue with mixing Jeppesen commercial data with manually compiled references is version control. Jeppesen updates its manuals on a twenty-eight-day cycle. AIP supplements and NOTAMs are updated continuously. Nethflight and similar aggregation services sometimes publish their own supplemental charts on irregular schedules. If you are doing manual cross-referencing, you need to know exactly which revision number each document came from and when it was last updated. I lost track of this on a flight into a regional airport in Eastern Europe once. The Jeppesen plate showed one VOR approach procedure. The AIP supplement showed a different final approach course because a navigation aid had been recalibrated two weeks earlier. The Nethflight reference I had used was a month old. We ended up conducting the approach using the AIP version after I realized the discrepancy at about eight thousand feet. No injury, no incident. Just a really uncomfortable hour of my life. That experience changed how I handle these hybrid workflows entirely. Now I treat the AIP or the official civil aviation authority publication as the source of truth and use Jeppesen and any manual compilations as supporting references. Never the other way around.
Get the Full Details
When This Workflow Actually Makes Sense
There are legitimate uses for combining these sources. Here are the situations where I found value in it: Operations into airports with limited Jeppesen coverage. Some smaller European and African airfields simply do not get full Jeppesen support. In those cases, pulling whatever manual data exists from alternative sources becomes necessary for safe planning. Temporary procedure changes that have not yet propagated. Sometimes a NOTAM will change an approach minimum or close a runway for construction. The next Jeppesen update cycle may not cover it immediately. Having a manual reference system means you can file around it until the next official update.
Cost-sensitive operations that cannot afford full electronic flight bag licensing. Some operators run aircraft with basic navigation equipment and rely on printed manuals because EFB solutions require certified hardware and ongoing subscription fees that make financial sense only for larger fleets.
Limitations and Where It Fails Completely
Let me be clear about where this manual cross-referencing approach breaks down. It does not scale. If you are planning more than five or six flights per week across different regions, the time investment becomes unsustainable. The error rate increases significantly because human visual comparison of chart data is inherently imperfect. I have seen experienced planners miss discrepancies that were clearly visible once pointed out. The workflow also assumes you have access to current AIP supplements and NOTAM systems for every region you operate into. If you are flying into countries where those resources are slow to publish or difficult to obtain in English, your manual compilation becomes unreliable regardless of how careful you are. The most honest recommendation I can give is this. Use the Jeppesen Instrument Commercial Manual Nethflight Rexair hybrid approach only when you have no better alternative. If your operator can invest in a certified electronic flight bag system with live data updates, do that instead. The cost difference between manual chart compilation and a proper EFB setup pays for itself within a few months of operation if you factor in pilot time and error reduction. For the occasional flight into marginal coverage areas, the manual method is acceptable. For regular operations, it is a liability you are carrying without realizing it. If you are committed to the manual route, the single most important practice is maintaining a revision log. Record the exact manual revision number, the date you received it, and the source document number for every approach plate you cross-reference. When someone asks you why a particular minimum was used during an audit, that log is the only thing that protects you. Without it, you are relying on memory. Memory fails under pressure. Paper does not.
