Another perfect sunset forms up west of the field at Lantana (KLNA). The light turns gold, the wind softens, and for a moment the ramp goes quiet in that way it only does between departures.
You’re in the left seat, engine off, logbook open.
The numbers look fine—dual, solo, night—but your pen pauses over one column:
Cross-Country.
Not because you don’t have the time; but because you’re not completely sure what counts. You’ve heard enough stories to hesitate. A pilot who logged every landing as cross-country—until a checkride turned into a cross-examination. Another who flew a perfect straight-in at night and spent a week wondering if it “counted.” Someone else who strung together short hops and hoped the FAA would see it their way.
If you’re working on your instrument rating, the question gets sharper: do those 50 hours of PIC cross-country change once you’re flying IFR? And if you’re on the CFI path, there’s a quieter pressure: one day, your signature is going to sit under someone else’s logbook entries.
So before the next engine start, it’s worth settling this—not just to pass a checkride, but to build a logbook that holds up under scrutiny.
Before diving into regulations, let’s try this:
Next time you plan a flight, ask yourself one question before anything else:
“Where does this flight begin?”
Not the leg you’re about to fly.
Not the last airport you landed at.
The original point of departure.
Because buried in 14 CFR §61.1(b)(3) is the line that quietly governs almost everything about cross-country time:
For the purposes of aeronautical experience, the landing must be at a point more than 50 nautical miles straight-line from the original point of departure.
That’s it.
Not distance flown.
Not number of legs.
Not whether you filed IFR.
Just a straight line—from where the flight began to where it ends.
If that idea feels simple, good. It should. But it’s also where most logging errors begin.
Picture a common South Florida evening:
You depart Lantana, stop in Stuart (KSUA, about 36nm north), land, grab a quick drink of water, and continue another 30nm or so to your final stop in Vero Beach (KVRB).
Each leg, on its own, doesn’t quite get there.
So here’s the question:
Did you just log zero cross-country time—or all of it?
The FAA answered that in Van Zanen (2009) interpretation:
The pilot determines what constitutes a “flight.”
Which means if you never ended the flight—never “reset” the clock—then the only distance that matters is from your original departure to your final landing.
If that final landing of the mission sits more than 50nm away, the entire sequence qualifies.
Not the last leg.
Not part of it.
Not even because it is or isn't separate logbook lines.
All of it—the entire flight... The entire mission.
Now flip the scenario.
Same route—but you shut down midway, log a flight, end the mission, then start a new one.
You’ve essentially just reset your “original departure.” The clock starts over. The distance shrinks. The qualification disappears.
Nothing about the airplane changed.
Only your definition of the flight did.
That’s the level this is operating on.
Close the canopy. Imagine you’re across the table from a DPE.
They’re not asking how the flight felt.
They’re asking how you logged it—what was the mission?
Under §61.51, your logbook isn’t just a diary—it’s a record you may have to defend.
So look at your last few entries and ask:
Did you identify the original departure?
Did you record the destination clearly?
Could someone verify the straight-line distance?
Did you note how you navigated?
A solid entry doesn’t try to impress. It removes doubt:
XC, KLNA—KSUA—KVRB, 65nm straight-line from original departure. Pilotage + VOR.
Full stop.
Or, under IFR:
IFR XC, KLNA—KSUA—KVRB, 65nm straight-line. GPS + VOR. Flight plan filed.
No extra words. No ambiguity. Including the stop at KSUA allows you to defend your extra landings along the way (as they may be needed for currency).
If someone questions it five years from now, that line and your notes should answer them.
At some point, usually during instrument training, a subtle assumption creeps in:
“This must be different under IFR.”
It isn’t.
The 50-hour PIC cross-country requirement in §61.65(d) uses the same definition as everything else. No alternate standard. No IFR exception.
Whether you’re navigating visually down the coastline or flying a filed route through the system, the same question applies:
Is the landing more than 50nm from where the flight began?
If not, it doesn’t count as cross-country time for experience requirements—no matter how complex the flight was.
That can be frustrating. It’s also intentional.
The FAA isn’t measuring workload. It’s measuring range and planning.
Some of the most persistent confusion comes from details that seem minor—until they show up on a checkride.
You’re on a long night cross-country. The destination is a towered airport. ATC gives you a straight-in.
No downwind. No base. Just a long final.
Does it count toward the required night landings for the certificate since they require a flight in the traffic pattern?
According to the Pilot/Controller Glossary and AIM 4-3-2, the idea of the traffic pattern is based on the flow of aircraft. A straight-in is simply an extended final within that flow.
So yes—it counts.
But here’s the better question:
Did you log it in a way that makes that clear?
During private pilot training, the long solo cross-country must total 150nm.
But that’s not quite exactly the same as the cross-country qualification.
The FAA clarified this in Keller (2009):
A triangular route can meet the 150nm total distance requirement—and still fail the cross-country definition—if no landing point is more than 50nm from the original departure. And as stated in 61.109, one segment, or leg, must also be greater than 50nm.
So ask yourself:
Does your flight satisfy both the total distance requirement and the 50nm rule?
If not, it doesn’t meet the standard.
In shared time (as a safety pilot supporting simulated instrument flight), it’s tempting to assume both pilots benefit equally.
But interpretations such as Hilliard and Gebhart (2009) draw a clear line:
Only the pilot who conducts the entire flight—from takeoff to landing—logs cross-country time for experience.
Not part of it. Not a segment.
All of it.
Let’s bring it back to Lantana. You’re planning tomorrow’s flight.
Before you check weather or fuel, try this:
Challenge 1
Pick a destination.
Now draw a straight line—not along your route, but directly—from Lantana to that airport.
Is it more than 50nm?
If yes, the flight can qualify.
If not, no amount of routing (excluding a landing somewhere else) will fix it.
Does it matter how many stops you made along the way? What if you made a few laps in the pattern before coming back? What was the mission?
Challenge 2
Build a multi-leg route using only short segments.
Now ask:
Will I treat this as one continuous flight—or several?
That decision determines whether it qualifies as a cross-country mission, right?
Challenge 3
Plan a night flight into a towered airport.
If you’re given a straight-in, will your logbook reflect that it was part of the traffic pattern?
Challenge 4 (Instrument Pilots)
Look at your last 10 hours of PIC time.
How much of it actually meets the 50nm cross-country definition?
Not estimated. Verified.
The CFI Perspective (Whether You’re There Yet or Not)
At some point, you may be the one teaching this.
Or signing for it.
And when you do, the standard changes slightly.
It’s no longer:
“Does this make sense to me?”
It becomes:
“Would this hold up in front of a DPE—or the FAA?”
Under §61.93 and guidance like AC 61-65, your endorsement isn’t just permission. It’s a statement that the student understands—and can apply—the rules correctly.
The best instructors don’t just explain cross-country time.
They make their students prove it. And something to think about, can you keep all that time you've been logging while you train your students on cross-country flights?
The pilots who never struggle with this aren’t guessing after the fact.
They’re deciding before engine start.
A simple mental check:
Where is my original departure?
Which landing point exceeds 50nm?
Does this meet the requirement I’m trying to satisfy?
How will I log it?
Ten seconds on the ground saves hours of confusion later.
The light is fading now. The ramp is quiet again. You close the logbook—but this time, the hesitation is gone.
Cross-country time isn’t a gray area anymore. It’s a system:
A definition in §61.1 that never changes.
Experience requirements in §61.109, §61.65, and §61.129 that shape how it’s used.
The semantics of wording like "straight-line distance," "cross-country," "total distance," and others.
Interpretations that explain how it works in real airplanes, on real days.
And a logbook that either supports your experience—or raises questions about it.
So next time you sit here, pen in hand, try this:
Before you write the number, ask yourself:
“If someone challenged this entry, could I defend it—clearly, simply, and without hesitation?”
If the answer is yes, you’re not just logging time.
You’re building a record that will carry you through every rating, every checkride, and every interview that follows.
And that’s what cross-country time is really for.
14 CFR 61.1(b)(3) — Core definitions and 50 NM straight-line rule (applies to instrument rating XC).
14 CFR 61.65(d) — Instrument rating: 50 hours PIC XC + specific IFR XC training flight (250 NM route, 3 approaches).
14 CFR 61.109 & 61.129 — PPL and CPL experience requirements, including “total straight-line distance” and pattern wording.
14 CFR 61.51 & Grannis (2016) — Logging mechanics and flight-time definition.
14 CFR 61.93 & AC 61-65J — Student endorsements and solo XC training.
Keller (2009) — PPL solo XC triangular-route clarification.
Van Zanen (2009) — Pilot’s choice of what constitutes “a flight” (including combining multiple short legs).
Hilliard/Gebhart/Glenn (2009) — Safety-pilot XC logging limits.
Pilot/Controller Glossary & AIM 4-3-2 — Traffic pattern definition.