PROJECTATC
Learn ATC / IFR clearances

Climb via SID or maintain on an IFR clearance

· FAA phraseology · JO 7110.65 4-3-2 · AIM 5-2-9 · examples from current charts

TL;DR — THE THREE FORMS
1. SID has a published top altitudeclimb via SID — say no altitude at all.
2. SID has published crossing restrictions but the top altitude is “assigned by ATC”climb via SID except maintain 14000.
3. SID is radar vectors (or starts with “climb on assigned heading for vectors…”) → plain maintain 5000 — never “climb via”.

Every IFR departure clearance answers the same five questions — the classic CRAFT mnemonic: Clearance limit, Route, Altitude, Frequency, Transponder. The altitude line is where most trainees slip, because what you say depends on how the SID is charted, not on habit. Since the FAA’s 2014 “climb via” change, there are exactly three possibilities.

Case 1 — published top altitude: “climb via SID”

Open the ZZOOO FOUR departure at San Diego (KSAN). The chart box says TOP ALTITUDE: JETS FL230 / TURBOPROPS 15000, and the route carries its own crossing and speed restrictions. Everything the pilot needs is printed — so the controller assigns none of it:

CLEARANCE DELIVERY “Delta two thirty-one, cleared to Atlanta, ZZOOO Four departure, Gila Bend transition, then as filed. Climb via SID. Departure frequency one one niner point six, squawk four seven zero one.”

No “maintain”. The SID is the altitude instruction: the pilot climbs to the published top altitude and meets every published restriction on the way. Adding “maintain FL230” on top of “climb via SID” is wrong — and saying “maintain 5000” instead would quietly cancel restrictions the procedure designer put there.

Case 2 — restrictions published, top “assigned by ATC”: “climb via SID except maintain”

Some SIDs publish crossing restrictions but leave the top altitude open — the chart reads TOP ALTITUDE: ASSIGNED BY ATC. San Diego’s PEBLE SIX is one: it requires crossing MELDY at or above 14 000, but ATC owns the stop altitude. The pilot still has to fly the restrictions, so “climb via” stays — with the altitude bolted on:

CLEARANCE DELIVERY “Southwest five twelve, cleared to Las Vegas, PEBLE Six departure, Santa Catalina transition, then as filed. Climb via SID, except maintain one four thousand. Departure frequency one one niner point six, squawk four six two two.”

Read that as: “fly the SID’s lateral path and meet its restrictions, and your top altitude — the thing the chart left blank — is 14 000”.

Case 3 — vector SIDs and hybrids: plain “maintain”, never “climb via”

A radar-vector SID has no route to fly from the runway — the KENNEDY FIVE at JFK is the classic example (“fly assigned heading, radar vectors to assigned route”). Many SIDs are hybrids that start the same way: every San Antonio (KSAT) departure begins “climb on assigned heading for vectors to…”, then joins a charted track. Per the FAA’s Climb Via guidance, “climb via” applies to neither. ATC assigns the altitude directly — usually the value printed in the route description:

CLEARANCE DELIVERY “JetBlue six oh four, cleared to Boston, Kennedy Five departure, then as filed. Maintain five thousand. Expect flight level three five zero one zero minutes after departure. Departure frequency one three five point niner, squawk one four five two.”

Same story at KSAT (“maintain 5000” is printed on every SID there) and at Boise, where the BOISE THREE’s own text climbs you to 16 000 on runway heading.

How do I know which case I’m in?

Look at the chartYou sayExample
TOP ALTITUDE box shows a number / flight level climb via SID ZZOOO4 (KSAN) — FL230 · DEEZZ6 (KJFK) — 5000
TOP ALTITUDE “assigned by ATC” and crossing restrictions on the route climb via SID except maintain (alt) PEBLE6, CWARD2, MMOTO2, FALCC1 (KSAN)
“Radar vectors” / “climb on assigned heading” in the route description maintain (alt) KENNEDY FIVE (KJFK) · every KSAT SID · BOISE THREE
Charted route but no restrictions and no top altitude maintain (alt) BORDER SEVEN (KSAN)

The readback: what you should hear

“Climb via” is one of the few phrases a pilot must read back verbatim. Listen for it — a readback of “maintain flight level two three zero” after you said “climb via SID” is a readback error, and it’s on you to catch it:

PILOT — CORRECT READBACK “Cleared to Atlanta, ZZOOO Four departure, Gila Bend transition, then as filed, climb via SID, departure one one niner point six, squawk four seven zero one, Delta two thirty-one.”

Common mistakes

Chart data referenced from FAA d-TPP / CIFP, current AIRAC cycle. SIDs get renumbered when they change (ZZOOO4 becomes ZZOOO5, etc.) — the logic above doesn’t change, but always brief from the current chart.

Practise the clearance at KSAN

ProjectATC puts you on Clearance Delivery with live traffic filing these exact SIDs — ZZOOO4, PEBLE6, the KENNEDY FIVE — and grades every clearance you issue, word by word. Pilot readbacks are spoken, and about 1 in 8 contains an error.

OPEN KSAN FREE