The Reddit thread touches on a real and well-documented shift in commercial airline takeoff procedure: the move from static takeoffs to rolling takeoffs. A static takeoff involves the aircraft coming to a full stop on the runway centerline, with the flight crew advancing thrust levers and allowing engines to stabilize at a high power setting for several seconds before releasing brakes. A rolling takeoff, by contrast, has the aircraft continue through the turn from the taxiway onto the runway without stopping, with thrust smoothly applied as the airplane is already moving. The original poster's memory of dramatic, rocket-like accelerations from a dead stop at O'Hare in winter is not childhood imagination — it reflects an actual procedural norm from roughly a decade or more ago that has since given way to rolling takeoffs as the default technique at most major airlines.
The shift is driven primarily by efficiency and operational tempo rather than performance considerations. Rolling takeoffs shave meaningful time off each departure — typically 20 to 30 seconds per flight when multiplied across an airline's entire schedule, this adds up to substantial fuel savings and improved on-time performance, particularly at high-throughput hub airports like O'Hare where runway occupancy time directly affects arrival and departure rates for air traffic control. Boeing and Airbus have both published guidance supporting rolling takeoffs as standard practice, and airlines have increasingly incorporated them into standard operating procedures over the past decade as fuel costs and schedule reliability became greater competitive pressures. The engine spool-up time is essentially absorbed into the taxi-to-runway transition rather than being a distinct, static phase.
That said, static, full-stop takeoffs have not disappeared entirely, and pilots reading this should recognize the specific conditions under which they still make sense or are required. Contaminated runway conditions — snow, slush, standing water, or ice, which would have been common during the poster's O'Hare winter flights — often necessitate a static application of takeoff thrust so the crew can verify engine parameters, symmetric thrust, and instrument indications are stable and normal before committing to the takeoff roll on a potentially slippery surface. Performance-limited takeoffs, short or obstacle-constrained runways, and certain company or regulatory requirements can also dictate a static start. Additionally, engine anti-ice usage, RTO (rejected takeoff) planning margins, and ATC sequencing (such as an immediate line-up-and-wait clearance versus a rolling clearance onto an active runway) all factor into whether a crew executes a rolling or static takeoff on any given departure.
For working pilots, this is a good reminder that "standard" procedure is airline- and condition-dependent, and that SOPs evolve based on data, not habit. Part 121 crews should be well-versed in their carrier's specific guidance on when rolling takeoffs are authorized versus when a static takeoff is required, since the decision isn't purely about efficiency — runway contamination reports, crosswind components, and performance calculations from the FMS or EFB all feed into that call. For business aviation and Part 91/135 operators, the same physics and considerations apply, though the pressure to shave seconds off ATC sequencing is generally lower, and static takeoffs on shorter runways or in performance-limiting conditions remain common and often prudent. The broader trend reflects an industry-wide push toward marginal efficiency gains — in fuel burn, schedule reliability, and runway throughput — that mirrors similar changes seen in single-engine taxi procedures, reduced APU usage, and continuous descent arrivals, all of which trade small, cumulative savings against operational complexity and crew workload.