Last Updated: June 4, 2026 | By the E3 Aviation Editorial Team
Most pilots think VFR cross-country planning died the day ForeFlight could plot a magenta line in three taps. It didn’t. The skill changed shape. It’s still the gate between an uneventful trip and a bad day. The bad day ends with a vector to the nearest field and a phone call to the FBO.
VFR cross-country planning in 2026 is a hybrid skill. You’re using an EFB for routing, weather, and weight and balance. You also have to know what the regs require. You have to know what the airplane can actually do. You have to know what to do when the tablet quits over a ridge. The pilots who plan well treat the magenta line as a starting point — not the plan itself.
This guide walks the full end-to-end VFR cross-country planning workflow. We teach it the same way inside the E3 Aviation Association community. Regs first. Then the route. Then the nav log. Then performance, weather, fuel, airspace, alternates, and the risk-management gate. Same sequence every trip. The repetition is the point.
Why VFR Cross-Country Planning Still Matters in 2026
We’ll be straight with you: most weekend pilots skip half the work and call it planning. They open ForeFlight, tap two airports, glance at the weather strip, and head to the airplane. That’s not planning. That’s launching.
VFR cross-country planning isn’t busywork. It’s the layer where you catch the things that will bite you in the air. A forecast trending toward MVFR. A fuel stop that closes at sundown. A 2,200-foot runway at field elevation 6,300. A tablet battery already at 41 percent. None of that shows up on the magenta line. All of it shows up in a real plan.
The other reason it still matters is regulatory. The FAA hasn’t relaxed 91.103 because EFBs exist. The preflight action standard is the same. Launch without becoming familiar with all available information for the route and you’re not legal. The slick app doesn’t change that.
What the FARs Actually Require Before Departure
Two regs anchor every VFR cross-country planning session. 14 CFR 91.103 is Preflight Action. 14 CFR 91.151 is Fuel Requirements for VFR Flight.
91.103 says the pilot in command shall become familiar with all available information concerning that flight. For any flight not in the vicinity of the departure airport, that information includes:
- Weather reports and forecasts for the route
- Fuel requirements for the planned trip
- Alternatives if the planned flight can’t be completed
- Any known traffic delays advised by ATC
- Runway lengths at airports of intended use
- Takeoff and landing distance data from the approved Flight Manual
That’s the floor — not the ceiling. A real VFR cross-country planning workflow goes deeper than the reg. The reg only describes the legal minimum. It doesn’t describe the safe one.

Start With the Route — Sectional Chart, Course Line, Checkpoints
Route planning starts on the sectional. Even if you skip paper, the sectional view in ForeFlight or Garmin Pilot is where VFR cross-country planning gets built. You’re drawing a course line. It has to avoid hostile terrain. It has to thread the airspace. It has to clear the obvious weather risks for the season.
Pick checkpoints along the line. Space them roughly 10 to 20 nautical miles apart. Closer spacing gives you more frequent position fixes; wider spacing means less workload. The checkpoints themselves matter — a major highway interchange or a unique lake is a checkpoint. A random road bend isn’t.
For deeper sectional chart fluency, the sectional chart guide walks every symbol you’ll use during this step.
Pilotage and Dead Reckoning — Still the Core Skill
The FAA hasn’t dropped pilotage and dead reckoning from the ACS. They’re still how you back up the GPS when the GPS gives up. Every VFR cross-country planning session should produce a route you could fly with the EFB off. Even if you never have to.
Pilotage
Pilotage is navigation by visual reference to ground landmarks. You match what’s on the sectional to what’s outside the window. Rivers, highways, towns, railroads, power lines, airports — anything distinctive enough to spot from altitude works.
Dead Reckoning
Dead reckoning is navigation by time, airspeed, distance, and direction. You start at a known point. You hold a heading. You fly a known groundspeed. You project where you should be at a given time. The estimate is only as good as the wind input — which is why the wind triangle matters.
The Wind Triangle
The wind triangle is the math behind every leg of a VFR cross-country planning nav log. True course plus wind correction angle gives you true heading. Add magnetic variation and deviation to get the compass heading. Solve the vector and you get groundspeed too. The E6B does this in a few rotations. ForeFlight does it the second you drop in winds aloft.
The Navigation Log — What Goes in Each Column
A nav log is the in-flight reference document VFR cross-country planning produces. It’s not optional — it’s the thing you actually look at after the runway falls behind you.
Standard columns include:
- Checkpoint — landmark name and distance from prior point
- Course (true and magnetic) — the line you’re trying to fly
- True airspeed — from the POH at planned altitude and power
- Wind direction and velocity — from the winds aloft forecast
- Wind correction angle — solved from the wind triangle
- True heading — true course plus WCA
- Magnetic heading — true heading plus magnetic variation
- Groundspeed — TAS adjusted for the wind component
- Distance — leg length in NM
- ETE — estimated time enroute per leg
- Fuel burn — gallons per leg at planned power
The nav log is also where the in-flight discipline lives. You note actual times at each checkpoint, compare to the estimate, and adjust early when reality drifts from the plan. That’s the whole game.

Performance Numbers From the POH
VFR cross-country planning isn’t done until you’ve pulled the actual takeoff and landing distances for the conditions you’ll see. That means density altitude at departure, density altitude at destination, and any en-route field you might use as an alternate.
For most piston singles, the takeoff distance chart wants pressure altitude, OAT, weight, and runway condition. A 1,200-foot ground roll at sea level on a 59°F day might double at 6,000 feet pressure altitude. Same airplane. Same weight. Different runway environment entirely.
The density altitude guide walks the math. It also covers the cognitive trap. Most pilots confuse field elevation with the number the airplane actually feels.
E6B vs ForeFlight — When to Use Each
Here’s what most pilots get wrong: they think the choice between an E6B and ForeFlight is about preference. It’s not. It’s about what the tool is for.
ForeFlight is the planning tool. You build the route. You drop in winds aloft. You get groundspeed and fuel burn per leg. You see the W&B forms populate. You export the nav log. The full VFR cross-country planning workflow runs in under fifteen minutes when the EFB is set up right.
The E6B is the backup tool — and the checkride tool. Every DPE we’ve sat with has asked the candidate to compute one leg by E6B during the oral. Not because they expect you to fly the trip that way. Because they want to confirm you understand what the airplane is doing when the EFB does it for you.
The ForeFlight complete guide walks the EFB side of this in detail. The E6B side stays in your flight bag because the iPad will quit at exactly the wrong moment one day.
The Weather Briefing in 2026
A real VFR cross-country planning weather briefing pulls three things. The route forecast. The airport observations and forecasts. The en-route hazards. In 2026 most pilots get all three through ForeFlight or 1800wxbrief.com. That’s fine — provided you actually read what comes back.
The route forecast covers what you’ll fly through. The METARs and TAFs at departure, en-route, and destination tell you what the airports are doing. The hazard products — AIRMETs, SIGMETs, convective SIGMETs, PIREPs — tell you what to avoid.
For the basics of METAR decoding, the METAR and TAF guide walks the alphabet soup. For VFR weather minimums by airspace, the VFR weather minimums reference covers what’s legal and what’s smart.
Fuel Planning Under 91.151 — Don’t Plan to the Floor
91.151 sets the legal floor for VFR fuel. You need enough to reach the first point of intended landing. Plus a reserve of 30 minutes during the day or 45 minutes at night. Both at normal cruise power. That’s a floor — not a flight plan.
Honestly, this is where we’d push back on the regulation. A 30-minute reserve in a 172 burning eight gallons per hour is four gallons. Four gallons is one go-around, one missed approach, and one taxi from the FBO to the fuel pump. That’s not a reserve — that’s a margin so thin you’ll find yourself sweating the magenta line into the destination.
The E3 Aviation house rule is simple: plan to one hour of reserve at cruise, not the legal minimum. That’s eight gallons in a 172. It’s a number you can explain to a checkride examiner. To your passengers. To yourself when the FBO tank is empty and the next field is forty miles away.
The other part of VFR cross-country planning fuel math is the climb. Climbing at full rich, full power, burns more than cruise. Most POHs publish a separate climb fuel-burn number. Use it. Don’t assume cruise economy on the leg you’re still pointed up.
NOTAMs and the Airspace You’ll Cross
NOTAMs are the regulatory product VFR cross-country planning skips most often — and the one that bites hardest. A closed runway. A TFR over the destination. A parachute jump zone live for the weekend. A class B veil with an unfamiliar SFRA. All of it lives in the NOTAM stack.
Pull NOTAMs for departure, en-route fields you’d actually use, and destination. ForeFlight surfaces them by airport. 1800wxbrief.com lets you query by route. Don’t rely on the headline summary — read the entries. The TFR that closed the destination yesterday might still be active when you check tomorrow.
Airspace planning runs in parallel. Identify every controlled airspace your magenta line crosses. Class B requires a clearance. Class C and D require two-way radio communication established. Class E and G have weather minimums but no clearance requirement. The airspace guide covers the rules for each class — required equipment, communication, and weather minimums included.
Airport Selection Along the Route — Diversion Options
Every VFR cross-country planning workflow should produce two or three named diversion airports spaced along the route. Not a generic “I’ll figure it out” plan. A specific list with frequencies, runway lengths, fuel availability, and field elevation noted.
The reason is simple. When weather goes down or the engine runs rough, you don’t want “the nearest airport.” You want a known field. One you already evaluated as suitable for your aircraft, your fuel state, and the conditions you’re actually in.
For each diversion candidate, confirm:
- Runway length adequate for landing distance plus a margin
- Fuel available and FBO hours (24-hour self-serve is a real difference-maker)
- Field elevation and density altitude implications
- Airspace and approach environment — towered or non-towered, CTAF or Tower frequency
- Distance and ETE from your current waypoint
Drop this into a column on the nav log. It’s eight more characters per checkpoint and turns a generic plan into one you can actually execute under pressure.
The PAVE Checklist Applied to the Cross-Country
The FAA’s PAVE checklist is the single best VFR cross-country planning risk-management gate. Pilot, Aircraft, enVironment, External pressures. Run it the night before and again on the morning of the trip.
- Pilot — IMSAFE check: Illness, Medication, Stress, Alcohol, Fatigue, Eating. Currency. Recency in type. Time since last cross-country.
- Aircraft — Airworthiness inspections current. Discrepancies in the squawk list addressed. Fuel state matches the plan. Weight and balance within envelope at takeoff and landing.
- enVironment — Weather along the route, at departure, at destination, and at every alternate. Terrain. Time of day. Daylight remaining at destination. Density altitude at the highest-elevation point.
- External pressures — The party at the destination. The customer waiting. The passenger who paid for the trip. Get-there-itis is the single most common factor in VFR-into-IMC accidents.
Score each item honestly. If any one of the four lights up, you’ve got a planning problem to solve before you start the engine. Not a justification to launch anyway.
Filing the VFR Flight Plan
Filing isn’t required for VFR — but the search-and-rescue protection it buys is worth the four minutes. Filing is the natural endpoint of VFR cross-country planning. The plan activates with FSS once you’re airborne. It closes when you call in at destination. If you don’t close, search procedures start 30 minutes after your estimated arrival.
The full filing workflow lives in the VFR flight plan guide. It covers ICAO Form 7233-4 fields. Plus the ForeFlight Dial button. Plus the three activation paths.
One reminder we make to every member: close the flight plan. The number of pilots who land, taxi, and trigger an INREQ at the 30-minute mark is higher than you’d think.
The In-Flight Plan — What Real Pilots Track
VFR cross-country planning extends into the cockpit. The plan you built on the ground is useful only if you actually use it once you’re airborne.
The basic in-flight discipline is the time-distance-fuel check at every checkpoint. Note the actual time over the point. Compare to the estimate. If you’re three minutes late at checkpoint two, you’ll be six minutes late at checkpoint four. Your fuel reserve at destination is shrinking with you.
The other thing real pilots track is the diversion clock. At every checkpoint, ask three things. If I had to divert right now, where would I go? How long would it take? Would I arrive with fuel in the tanks? If the answer to any of those is fuzzy, the plan isn’t living up to the work you put in.
Common VFR Cross-Country Planning Mistakes
Five mistakes account for most of the planning failures we see in member trip reviews:
- Trusting the magenta line. ForeFlight will route a 172 across a 12,500-foot ridge in summer because the line is the shortest distance. The line doesn’t know the airplane.
- Skipping the POH performance step. Density altitude at a high-elevation destination changes takeoff and landing distances by hundreds of feet. Pulling the actual numbers takes three minutes.
- Planning to the legal fuel floor. 30-minute reserve is the regulatory minimum. It’s not the planning minimum. Add 30 more.
- One alternate, generic. “I’ll divert if I need to” isn’t an alternate. A named field with runway, fuel, and frequency noted is.
- Skipping NOTAMs because the EFB headline looked clean. The TFR that grounds the trip is usually buried below the headline. Read the full stack.
Building a VFR Cross-Country Planning Routine
The pilots who plan well don’t have more discipline than the rest. They have a routine. Every trip starts the same way. Every step happens in the same order. The parts that used to take an hour now take twenty minutes.
Our recommended VFR cross-country planning sequence:
- Pull route weather and the airport observations and forecasts. If anything is borderline, stop here and reassess.
- Build the route in ForeFlight. Add checkpoints 10–20 NM apart along the line.
- Pull POH performance numbers for the conditions you’ll see — takeoff, climb, cruise, descent, landing.
- Drop in winds aloft. Verify groundspeed and fuel burn per leg.
- Pull NOTAMs for departure, en-route, and destination. Read each entry.
- Identify two or three diversion airports. Note runway, fuel, frequency, elevation.
- Run the PAVE checklist. Score each element honestly.
- File the VFR flight plan. ForeFlight or 1800wxbrief.
- Brief the passengers — sterile cockpit during taxi, climb, and descent.
- Print or screenshot the nav log so a dead tablet doesn’t kill the plan.
The whole VFR cross-country planning workflow shouldn’t take more than 30 minutes once the routine is yours. The work compounds across trips — every plan you build makes the next one faster.
Our Take on Planning in the EFB Era
Here’s our take: ForeFlight didn’t kill VFR cross-country planning. It killed bad planning. Pilots who used to plot by hand and still launched thin now have a tool that does the math faster. The ones who used to skip steps still skip them. They just do it with prettier graphics.
The fix isn’t going back to paper. The fix is treating the EFB as the calculator and the pilot as the planner. The magenta line is what the math produced. The plan is the set of decisions you made about what to do when the line stops working.
Build the plan that survives the EFB quitting, the weather deteriorating, or the destination closing. Then go fly. That’s the E3 Aviation standard, and it’s what we teach inside the community. Join the E3 Aviation Association for the full planning library. Plus monthly member fly-outs. Plus the trip-review network that turns planning theory into airmanship.
FAQ
How long does proper VFR cross-country planning take in 2026?
A clean, repeatable VFR cross-country planning workflow runs about 30 minutes once you have a routine. First-time planning for a new route or unfamiliar aircraft takes longer — closer to 60 minutes. You’re learning the airplane’s performance numbers, the route’s terrain, and the airspace all at once.
Do I really need a paper nav log if I’m flying with ForeFlight?
You need some backup. A printed nav log works. A screenshot saved to the home screen works. A second device with the route loaded works. The reason isn’t regulation. Tablets overheat. Batteries quit. Lightning hits at the wrong moment. The nav log is what keeps you flying when the EFB doesn’t.
Is the 30-minute VFR fuel reserve actually enough?
It’s the legal minimum under 91.151 — but it’s not a planning target. A 30-minute reserve in a 172 is roughly four gallons. One missed approach, one go-around, or one slow taxi can eat through it. Plan to a one-hour reserve at cruise as a habit. The cost is a small fuel weight penalty. The benefit is real margin when something doesn’t go to plan.
Further Reading
- How to File a VFR Flight Plan
- How to Read a Sectional Chart
- How to Read a METAR and TAF
- VFR Weather Minimums Every Pilot Must Know
- Understanding Class B, C, D, and E Airspace
- ForeFlight Complete Guide for GA Pilots
- Density Altitude Complete Guide
- Cessna 172 Complete Pilot Guide
- Aircraft V-Speeds Quick Reference
- Holding Pattern Entry Procedures

