Close dual XC, dual night, and night-XC in one flight

Three of the most common shortfalls on a PPL ASEL packet show up together: dual cross-country time (§ 61.109(a)(1)), dual night time (§ 61.109(a)(2)), and the dual night cross-country flight that has to total more than 100 NM (§ 61.109(a)(2)(i)). A well-planned single dual flight can satisfy all three at once and bank a chunk of the ten night takeoffs and full-stop landings (§ 61.109(a)(2)(ii)) on the way home.

What the regulation actually requires

• § 61.109(a)(1): 3 hours of cross-country flight training. Cross-country here is the § 61.1(b)(3) flavor — a landing more than 50 NM straight-line from the original point of departure.
• § 61.109(a)(2): 3 hours of night flight training.
• § 61.109(a)(2)(i): one night cross-country whose total route distance exceeds 100 NM.
• § 61.109(a)(2)(ii): 10 night takeoffs and full-stop landings, with each flight involving a traffic-pattern phase at an airport.

A flight that closes all three

Pick a destination at least 55 NM straight-line away (so the leg comfortably exceeds the 50 NM XC floor) and route the return leg through a second waypoint so the round-trip total exceeds 100 NM. Depart after evening civil twilight at your home field. Plan a full-stop landing at the destination — that is one of your ten night T&Ls — and then return.

On the return, divert to a third airport with an operating control tower (or a non-towered field if you've already covered § 61.109(a)(5)(iii)) and stay in the pattern for the remaining T&Ls you need that night. Even if you only get four or five done before fatigue sets in, you've cleared the cross-country, the night minimum, the > 100 NM night XC, and meaningfully chipped at the ten T&L count.

Logging it so the packet sees it

• Log dual time, night time, cross-country time, and (for the destination and tower stops) night landings as separate columns — most logbooks have all four.
• Use route notation that names every airport touched (e.g. KSQL-KSCK-KOAK), so the cross-country verifier can re-derive the > 50 NM and > 100 NM checks without ambiguity.
• Record full-stop night landings as full-stop in the night-landings column, not as the night-T&L column some software defaults to. Touch-and-goes do not satisfy § 61.109(a)(2)(ii).