How early should you arrive at St. Louis Lambert International Airport (STL)?

Avoid both over-buffering and cutting STL too close

A mid-size airport can be quick on one trip and slower on another. Start with the steps you actually need—parking or drop-off, bags, security and terminal navigation—then add only the contingency you want.

Is two hours enough at STL?

Two hours can be a useful rule of thumb, but the better question is what needs to happen between reaching St. Louis Lambert International Airport and being ready at the gate. A carry-on and curb drop-off can produce a very different plan from checked luggage, parking or an unfamiliar terminal.

A lower typical security range at STL is not a guarantee

FlyBuffer currently uses 5–15 min as the planning context for STL. A relatively low range can reduce the security allowance on a normal trip, but peak periods, checked bags, airline deadlines or unusual conditions can still justify more margin.

Airfield and passenger flow are separate parts of the STL trip

The current airport profile lists 4 active runways at STL. Runway capacity does not tell you how long security or parking will take, so FlyBuffer keeps airfield context separate from the passenger-side steps that determine when you should leave.

Why STL can feel different from both small airports and major hubs

At about 7,194,745 annual enplanements, STL occupies a middle ground: it may be easier to move through than the largest hubs, while still having enough passenger flow for time-of-day pressure to matter. Build the plan from the actual steps in your trip.

Checked bags and international departures

A checked bag can move the plan earlier because processing takes time and airlines may stop accepting bags before departure. International trips can also require more document and gate-ready time. Airline-specific check-in, bag-drop and boarding requirements always take priority over a general planning estimate.

When to add more contingency

Add margin when several variable steps stack together—for example off-site parking plus a checked bag, an unfamiliar terminal plus a wider security range, or an international flight with an airline cutoff.

When to recalculate your STL plan

Recalculate if your road journey changes materially, you switch from drop-off to parking, you add a checked bag, airport operations deteriorate or you find a better current security estimate. The recommendation is most useful when the inputs still match the trip you are taking.

STL profile snapshot: St Louis, MO

The current FlyBuffer dataset places STL in St Louis, MO, with 7,194,745 annual FAA enplanements and 4 active runways, with a longest published runway of 11,020 ft. Those facts are descriptive context, not a live queue measurement; they help keep the departure model anchored to this airport instead of copying a generic hub profile.

STL has a lighter passenger profile within FlyBuffer’s current set

With 7,194,745 annual enplanements, STL ranks #32 of 501 airports currently covered by FlyBuffer, below the set median of 76,729. A lighter passenger profile can reduce some airport-side pressure, but checked-bag deadlines, access transfers and peak checkpoint periods remain independent reasons to add time.

Nearby airport context around STL

BLV (Scott AFB/Midamerica Airport) is about 32 straight-line miles southeast and has a small passenger profile in the same dataset. COU (Columbia Regional Airport) is about 100 straight-line miles west and has a small passenger profile in the same dataset. Straight-line distance is only geographic context, not driving time; use your actual ground journey before treating another airport as a practical substitute.

How STL security compares with nearby FlyBuffer airports

FlyBuffer currently uses 5–15 min for STL. BLV is 5–10 min (in a broadly similar planning band); COU is 5–10 min (in a broadly similar planning band). These are airport-level planning ranges, not a reason to choose an airport on security alone; total ground travel and airport access can outweigh a modest checkpoint difference.

STL departure FAQ