The Reddit thread raises a question that touches on a fundamental but often misunderstood aspect of the National Airspace System: how general aviation traffic is integrated—or effectively excluded—from operations at the nation's busiest commercial hubs. The short answer is that there are no separate runways designated by aircraft category at airports like ORD, ATL, DFW, LAX, JFK, LGA, or DCA. Runways at these fields are shared infrastructure, and ATC sequences all arrivals and departures, regardless of whether the aircraft is a Boeing 777 or a Cessna 172, into the same traffic flow. What actually limits GA presence at these airports isn't regulation prohibiting light aircraft from landing, but rather the practical reality of slot controls, high landing fees, long taxi distances, and the operational friction of inserting a 120-knot piston single into a stream of jets flying 160-180 knots on final. A handful of these airports—LGA, DCA, and JFK notably—are subject to FAA slot restrictions or perimeter rules that directly limit total operations, which further squeezes out non-scheduled GA traffic by default rather than by explicit design.
For working pilots, this distinction matters operationally. Airline and corporate jet crews flying into slot-controlled or high-density airports rarely encounter light GA traffic sharing their runways, but they do encounter GA and business aviation traffic at reliever airports nearby (e.g., Chicago Executive or DuPage instead of ORD, Van Nuys instead of LAX, Addison or Love Field instead of DFW). This bifurcation is largely market-driven: FBOs, fuel costs, and ATC sequencing all push piston and light turbine traffic toward satellite fields, while the major hub's approach and departure procedures, minimum speeds, and required equipage (RNAV/RNP, ADS-B, sometimes RVSM-capable avionics on certain routes) create a de facto filter. Controllers can and do accept a slower aircraft into the sequence, but doing so introduces spacing penalties that ripple through an already tightly choreographed arrival bank—something controllers try to avoid during peak pushes, and something GA pilots flying into these fields need to understand before requesting such an operation.
The broader trend here reflects the increasing specialization of U.S. airspace and airport infrastructure. As commercial and cargo volumes have grown, the FAA and airport authorities have leaned harder into demand management tools—slot allocation, PBN-based arrival streams, and airspace redesign initiatives like the ongoing Northeast Corridor and Houston metroplex work—that are optimized for high-throughput, similarly-performing aircraft. This same dynamic explains why business aviation has increasingly consolidated at dedicated GA-friendly reliever airports and why NBAA and AOPA continue to advocate for protecting access to those fields as urban development pressures threaten to close or repurpose them. For corporate and charter pilots, understanding this ecosystem is essential flight-planning knowledge: choosing to fly into a Class B primary versus a reliever isn't just about convenience for passengers, it's about accepting longer taxi times, potential ground stops, and integration into an arrival flow built around jet performance profiles.
Ultimately, the question underscores a a widely-held public misconception—that airports have physically segregated "GA runways" and "airline runways"—when in reality the segregation happens upstream, through economics, infrastructure choices, and airspace procedures rather than through hard regulatory bans on light aircraft. Pilots transitioning from GA into commercial or corporate flying quickly learn that the real barrier to hub-airport access isn't a rule in the FARs, but the practical demands of flying compatibly with jet traffic in one of the most tightly managed airspace environments in the world.