1. Introduction

1.1. Problem context

Low-level wind shear has been a causal factor in some of the most severe takeoff and landing accidents in commercial aviation, with more than 1,400 worldwide fatalities since 1943 (McCarthy et al., 2022). National Transportation Safety Board (NTSB) investigations of catastrophic accidents — Eastern 66 at JFK (NTSB, 1976), Pan Am 759 at New Orleans (NTSB, 1983), Delta 191 at Dallas/Fort Worth (NTSB, 1986) — prompted the Joint Airport Weather Studies (JAWS) field campaigns (McCarthy, Wilson, and Fujita, 1982) and Fujita’s’s (1985) characterization of the microburst phenomenon, which in turn drove the development of ground-based Low-Level Windshear Alert Systems (LLWAS), airborne Predictive Wind Shear (PWS) systems, and crew training programs that have greatly reduced the risk (Evans and Ducot, 1994).

Yet hazardous encounters persist. The National Oceanic and Atmospheric Administration (NOAA) Storm Events Database lists 914 microburst reports in the United States between 2000 and 2020 (Romanic, Taszarek, and Brooks, 2022), with only 5–15 seconds typically available for recognition and response per the Federal Aviation Administration (FAA, 1988). In many cases the first observable symptom is not an alert but abnormally slow airspeed increase (“airspeed stagnation”).

Modern transport-category aircraft may carry two complementary wind shear protection systems: a predictive system, which uses weather-radar Doppler processing to detect shear ahead of the aircraft (Airbus, 2015), and a reactive system, which compares inertial and aerodynamic data to identify an actual shear encounter in progress. Neither system, however, provides continuous coverage during the takeoff ground roll. On the A320 family, predictive alerts are inhibited above 100 knots (kt) and up to 50 feet (ft) radio altitude, while reactive detection activates only 3 seconds after liftoff (Airbus, 2019).

On the Boeing 737, new predictive caution alerts are inhibited between 80 kt and 400 ft radio altitude, new warning alerts between 100 kt and 50 ft radio altitude, and ground proximity warning system (GPWS)-based reactive detection begins at rotation (Boeing, 2018). Many regional jets and older transport aircraft lack predictive wind shear capability entirely.

The result is a detection gap during the highest-energy portion of the ground roll — the regime between 80–100 kt and V₁ — in which crews have no automated warning and must rely on their own recognition of airspeed stagnation.

This recognition task is itself challenging. Indicated airspeed responds to pressure changes with a finite lag—0.3–1.0 s depending on installation, as characterized by Gracey (1980) and Houck and McIntyre (1998)—so a rapidly evolving shear may briefly mask the onset of performance loss. Section 3.2 examines this latency in detail.

The approach and landing phases, which the International Civil Aviation Organization (ICAO, 2005) identifies as historically accounting for the majority of wind-shear-related accidents, benefit from predictive and reactive alerts, stabilized energy states, and established go-around options explicitly trained for wind shear recovery.

In contrast, the takeoff roll offers no comparable safety net: the aircraft operates near maximum weight with rapidly increasing kinetic energy within a narrowing distance margin, leaving the pilot with no quantitative ground-referenced cue for the abort decision. IAS remains a reliable measure of aerodynamic capability—it correctly indicates whether the aircraft can fly—but during wind shear it ceases to reflect the ground-referenced energy state that governs stopping distance.

1.2. The V₁ decision framework under certification

Under 14 Code of Federal Regulations (CFR) §25.107 (FAA, 2025a) and European Union Aviation Safety Agency (EASA) Certification Specifications (CS) 25.107 (EASA, 2023a), V₁ is both the maximum speed at which the pilot can stop within the accelerate-stop distance available (ASDA) and the minimum speed at which takeoff can continue following critical engine failure. The V₁ computation integrates ASDA, takeoff distance available (TODA), aircraft mass, atmospheric conditions (density ratio σ), runway condition, wind component, slope, configuration, and obstacle clearance; the result satisfies all regulatory constraints including minimum control speed on ground (V_MCG), maximum brake energy speed (V_MBE), and tire-speed limits.

Accelerate-stop calculations include a two-second pilot reaction interval reflecting real-world variability (FAA, 1998).

Standard operating procedures (SOPs) typically structure rejected-takeoff decisions around defined speed regimes: below an operator-defined transition speed—commonly 80 kt for Boeing fleets and 100 kt for Airbus fleets—crews are trained to reject for any condition affecting safe flight; above that transition speed and up to V₁ (the high-energy regime), crews reject only for critical conditions such as engine failure, fire, wind shear, or when the aircraft is unsafe or unable to fly; above V₁, the expectation is to continue unless the aircraft is clearly incapable of flight.

This doctrine reflects the central trade-off between the risk of a high-speed rejected takeoff (potential runway excursion, tire or brake failure, or loss of separation) and the risk of continued takeoff with degraded capability. The V₁ speed represents the optimum balance point under certification assumptions: below V₁, stopping is guaranteed within available runway; above V₁, continuing with engine failure is feasible.

1.3. The wind shear decision gap

During a wind shear encounter, indicated airspeed remains a valid measurement of dynamic pressure; what changes is that the assumptions embedded in the precomputed V₁ may no longer be satisfied. When IAS stagnates despite sustained takeoff thrust, the crew’s primary speed reference decouples from the aircraft’s kinetic energy state: groundspeed—and therefore stopping energy—continues to increase while the airspeed indication flatlines.

The aerodynamic capability (governed by dynamic pressure and IAS) remains as designed, but the ground-referenced energy state—which determines stopping distance—diverges from what the crew observes on the airspeed tape.

The preflight V₁ as an operational decision boundary becomes unreliable not because IAS is false, but because the performance basis for V₁ has been violated by the wind-shear-altered airflow. The pilot is looking at valid instruments that no longer tell the whole truth.

ICAO and major manufacturers have recognized the decision-making challenges associated with this condition. Airbus acknowledges that when wind shear is detected during the takeoff roll, “the pilot may have to rely on his/her own judgment to assess if there is sufficient runway remaining to stop the aircraft” (Airbus, 2015). ICAO notes that “the go/no-go criteria based on engine-failure decision speed (V₁) may not be valid for wind shear conditions, since ground speed can be much higher than airspeed” (ICAO, 2005).

National Aeronautics and Space Administration (NASA) analysis found that “attainment of V₁ in a wind shear condition does not necessarily assure that the aircraft can be safely stopped on the runway” (Zweifel, 1988). Yet despite these acknowledgments, neither ICAO guidance documents nor manufacturer flight crew operating manuals provide a specific quantitative method for crews to express V₁ in ground-referenced terms when IAS becomes stagnated due to atmospheric phenomena.

Human factors research underscores the consequences of decision ambiguity. In a NASA-sponsored think-aloud study, Fischer, Orasanu, and Davison (2008) presented 61 airline pilots with conflicting wind shear pilot reports before departure: 73.7 % chose to depart despite the reported shear. The finding illustrates not recklessness but interpretive variability—pilots who saw the same cues reached opposite conclusions about the level of threat.

Separately, analysis of hull-loss accidents found that plan-continuation errors accounted for roughly three quarters of tactical decision failures, predominantly during approach and landing where cues were ambiguous and workload was high (Orasanu and Davison, 2001). The takeoff-roll wind shear scenario shares these same characteristics—ambiguous cues, high workload, and no quantitative threshold—suggesting that a pre-briefed GSV₁ gate could reduce interpretive variability. Whether it does so in practice is an empirical question addressed by the simulator studies proposed in Section 7.2.

2. Literature review

2.1. Related work

Several related research streams have addressed aspects of wind shear detection, takeoff performance monitoring, and optimal escape trajectories. None, however, has proposed a crew-usable, pre-briefable groundspeed decision threshold for the takeoff abort/continue decision during IAS stagnation. A systematic review of the most relevant prior work establishes this gap.

Wind shear detection and performance monitoring. Foy (1981) first evaluated groundspeed–airspeed differences as a shear indicator for approach operations. Proctor, Hinton, and Bowles (2000) developed the F-factor hazard index—now the FAA-certified standard for onboard reactive detection—which quantifies instantaneous energy loss rate. These systems detect shear presence but do not provide a crew decision threshold for the abort/continue choice. NASA’s takeoff performance monitoring system (TOPMS) (Middleton, Srivatsan, and Person, 1994) used GPS-derived groundspeed for real-time GO/ABORT advisories based on acceleration monitoring; it addressed deficiency detection rather than wind shear specifically and was not adopted by manufacturers.

A subsequent EUROCAE working group (WG-94) on takeoff performance monitoring system (TOPMS) standardization was unable to define performance requirements, partly due to technology maturity and the persistent false-alarm/workload trade-off (EASA, 2025b): a monitor that triggers unnecessary high-speed rejects can itself increase risk (EASA, 2025b). Jones (2019) proposed a Takeoff Performance Indicator (TOPI) concept using real-time wind component, but it requires hardware integration and does not derive the groundspeed–V₁ relationship from Part 25 physics. More recently, EASA (2025b) has proposed requiring takeoff performance monitoring systems on large aeroplanes under Notice of Proposed Amendment (NPA) 2025-01 (RMT.0741).

The proposal documents Airbus’s certified Take-Off Monitoring (TOM) function, operational on A350 and A380 fleets, which compares expected and actual acceleration from 30 kt and alerts crews at 90 kt if degradation exceeds 15%. Boeing and Embraer are developing equivalent functions. These acceleration monitoring systems detect data-entry errors, position errors, and engine degradation but do not address the IAS–groundspeed energy divergence specific to wind shear during the takeoff roll.

Trajectory optimization and stopping-distance analysis. Miele, Wang, and Melvin (1986) established theoretical performance limits for microburst encounters through variational methods; Stratton and Stengel (1995) developed a Bayesian risk-fusion system for wind shear avoidance. Neither produced a crew-briefable threshold. Zweifel (1990) conducted the only published simulation of stopping distance during takeoff-roll wind shear (Boeing 727, five surfaces), confirming shear magnitude as the dominant factor but not deriving a crew decision criterion. Gonzalez and Lombaerts (2023) analyzed V₁ sensitivity to environmental conditions without addressing IAS stagnation.

Notably, groundspeed-based speed protection already exists in another flight phase: Airbus’s Groundspeed Mini function uses ground-referenced speed to set a minimum selectable approach speed, and is accepted by regulators (Airbus, 2015). No analogous function exists for the takeoff roll.

Accident investigations and recent developments. Investigation reports consistently document the gap. The Air Accidents Investigation Branch (AAIB) East Midlands investigation (AAIB, 2020) found the manufacturer’s response emphasized pilot judgment with no quantitative thresholds; the Australian Transport Safety Bureau (ATSB) Perth investigation (2013) documented a crew that continued and cleared the runway end at 10 ft radio altitude. The Flight Safety Foundation (FSF, 2017) documented a case where IAS stopped increasing for several seconds with no alerts recorded.

While onboard detection remains limited, ground-based wind shear sensing has advanced considerably: coherent Doppler light detection and ranging (LIDAR) systems now provide airport-area coverage, as demonstrated by Chan (2012) and Zhang et al. (2022), and machine-learning severity classifiers applied to LIDAR data have achieved detection probabilities above 90%, notably in the work of Hon (2020) and Khattak et al. (2024). These systems improve situational awareness before takeoff but do not assist the crew once the roll has begun.

More broadly, Van Es (2010) found that about 50% of high-speed rejected-takeoff decisions across all causes were judged incorrect in hindsight, underscoring the difficulty of time-critical abort decisions even when cues are unambiguous. The wind shear scenario compounds this difficulty by removing the crew’s primary quantitative reference. Yet no published work provides a crew-briefable groundspeed threshold for the takeoff abort decision during IAS stagnation.

2.2. Contribution

Table 1 summarizes the approaches reviewed above and identifies, for each, the specific gap that remains. A common pattern emerges: existing systems and guidance either detect wind shear without providing an abort criterion, or address acceleration deficiency rather than the IAS–groundspeed energy divergence that characterizes a wind shear encounter during the takeoff roll.

Table 1: Literature gap analysis: existing approaches and the gap addressed by this paper.

The operational significance of this gap becomes apparent when the FAA’s severe-wind-shear threshold of 15 kt airspeed change (FAA, 1988) is expressed in time. Near V₁, average ground-roll acceleration computed from the Daidzic (2016) energy-balance model ranges from approximately 2.7 kt/s for a heavy widebody at reduced thrust to over 6 kt/s for a lighter narrowbody at full takeoff thrust (Fig. 1), so a 15-kt IAS stagnation takes roughly 2.5–6 seconds to develop. That interval is comparable to the time required for human recognition of unexpected instrument anomalies (Wickens, 2002), and falls within the detection-gap window during which automated alerts are inhibited (Section 1.1).

Once wind shear is recognized, the critical question is whether the aircraft can stop given its current ground-referenced energy state. The existing framework offers no quantitative answer during IAS stagnation, because the conventional V₁ cue has ceased to track the aircraft’s true kinetic energy relative to the runway.

This paper makes three contributions. First, we derive a physics-based method for expressing the certificated V₁ energy state in ground-referenced terms (Section 3). Second, we operationalize it through standardized crew procedures and a conservative interim heuristic (Section 4). Third, we map an implementation pathway through existing regulatory channels (Section 6) and outline a validation program as a prerequisite for operational adoption (Section 7).

3. Theoretical model

The physical model rests on standard aerodynamic and Newtonian mechanics as treated by Anderson (2016) and Hurt (1965). The underlying physics—how indicated airspeed, true airspeed, and groundspeed relate to the energy states governing stopping performance—are elementary. What has been missing is a systematic way to apply them at the operational level during wind shear.

The derivation intentionally employs closed-form equations suitable for operational use. The simplifications involved, and the reason they do not compromise the method, are addressed after the core result is derived (Section 3.1).

3.1. Energy and stopping distance

The kinetic energy at the reject-decision point may be written in integral form as:

where the integral represents the incremental work required to accelerate the aircraft of mass m from rest to groundspeed V₀. This energy must be dissipated to bring the aircraft to a complete stop on the runway. Wheel brakes dissipate this energy primarily through friction work at the tire–runway interface:

where μ(λ,V) is the slip-controlled tire friction coefficient as a function of slip ratio λ and velocity V, W is weight, L(V) is residual lift (decreasing with speed as dynamic pressure decreases), and s is the stopping distance. For closed-form analysis, consistent with the equivalent-deceleration approach used in certified accelerate–stop performance, an effective friction coefficient μ_eff is adopted. This coefficient represents the time-averaged deceleration capability and incorporates the complex dynamics of tire slip control, lift effects, and aerodynamic drag:

Here, μ_eff represents the certified equivalent deceleration used in transport accelerate–stop performance, incorporating antiskid modulation, lift dump, speed-dependent drag, and reverse thrust effects. Equating initial kinetic energy to braking work and solving for stopping distance:

Thus, stopping distance increases with the square of groundspeed and decreases with effective runway friction. This relationship exists entirely in the Earth-fixed frame, reinforcing that during wind-shear-induced IAS stagnation, the correct reference for stopping feasibility is governed by ground-referenced kinetic energy, not indicated airspeed.

The quadratic dependence on groundspeed matters: a 10% increase in groundspeed (e.g., from 140 kt to 154 kt) produces a 21% increase in required stopping distance.

A reasonable objection is that the closed-form model is too simple—real rejected takeoff (RTO) performance includes speed-dependent aerodynamic drag, residual lift effects, thrust reverser contribution, brake-temperature limits, and runway slope.

The GSV₁ method does not need to model these individually because the certificated V₁ already accounts for them. The method simply expresses that certificated energy state in groundspeed terms, preserving all the fidelity and safety margins already embedded in the manufacturer’s performance data.

A separate question is whether wind shear persisting after the reject decision could invalidate the certified stop margin. The effect is small, because wheel braking—not aerodynamic drag—dominates the ground roll. The force decomposition in the FAA Takeoff Safety Training Aid (Boeing, 1992) quantifies this: for a representative twin-engine transport at approximately 124 kt with speedbrakes deployed and no thrust reversers, wheel brakes account for approximately 87% of total retarding force, with aerodynamic drag contributing the remaining 13%.

Certified dry-runway accelerate–stop distances already exclude reverse thrust credit per 14 CFR §25.109(f)(1), so the only air-mass-sensitive force in the certified stop is aerodynamic drag—the 13% component. The 87% contributed by wheel braking is ground-referenced and largely unaffected by post-reject wind variations.

To verify this robustness quantitatively and assess its sensitivity to wind shear, we construct a first-principles deceleration model for a B737-800 at maximum takeoff weight on a dry runway with ground spoilers deployed and no reverse thrust—the same conditions specified in the Boeing (1992) training aid. Wheel braking force is computed as F_brake = μ_B(W − L), using the Daidzic (2016) effective braking coefficient (μ_B = 0.305, Eq. 5), which incorporates tire–surface friction, brake effort, anti-skid efficiency, and effective weight transfer. Aerodynamic drag is derived from a speed-dependent drag polar (Raymer, 2018) with ground-effect correction using the Prandtl–Wieselsberger influence coefficient (Mantle, 2016). Wind shear is modeled as a sustained tailwind shift—the most conservative assumption, as it maximizes the reduction in aerodynamic forces throughout the entire ground roll.

Under zero wind, the model predicts that wheel braking contributes 86.7% of total retarding force at 124 kt, closely matching the 87% derived from force data in the Boeing (1992) training aid. Introducing a 60-kt sustained tailwind reduces total deceleration by only 7.1%, adding approximately 171 ft (52 m) to the stopping distance at V₁ = 150 kt. The additional distance, while not negligible on a balanced field, falls within the conservatism already embedded in the certificated accelerate–stop distance: no reverse-thrust credit (14 CFR §25.109), a two-second recognition time, and conservative tire–surface friction assumptions. Moreover, when wind shear is forecast, operational practice adds further margin through longer runway selection, weight restrictions, and conservative wind assumptions in the takeoff performance computation.

3.2. Groundspeed availability and instrument lag

Groundspeed is available from two independent onboard sources: Inertial Reference Systems (IRS), integrating inertial measurements relative to Earth, and Global Navigation Satellite Systems (GNSS), determining velocity from satellite-based solutions (Grewal et al., 2001). Both are independent of air-mass motion. Modern transport-category aircraft carry redundant IRS units (typically two or three), and GNSS/IRS fusion provides an accurate combined estimate.

For indicated airspeed, three sources of delay accumulate in series: pneumatic propagation through pitot-static tubing, approximately 0.3 s for conventional tubing (Gracey, 1980); digital filtering in the air data computer (ADC), 0.4–0.7 s (Houck and McIntyre, 1998); and Aeronautical Radio, Incorporated (ARINC) 429 bus transmission, 50–125 ms (Thommen, 2016). For conventional installations these components sum to approximately 0.75–1.13 s. Smart-probe architectures (integrated pitot-static sensors with on-board processing) largely eliminate the pneumatic propagation delay, reducing the lower bound to approximately 0.45 s.

The combined IAS probe-to-display latency therefore ranges from 0.45 s (smart probe) to approximately 1.0 s (conventional tubing with optimized filtering) for current transport-category installations.

For groundspeed, the signal chain is entirely different. IRS units compute velocity by integrating accelerometer measurements at 50 Hz (Honeywell, 2016), independent of air-mass dynamics; flight-test measurements show a total transport delay of approximately 80 ms (NCAR, 2023). GNSS receivers independently determine velocity from Doppler shift with ≤0.2 m/s (≈0.4 kt) accuracy at the 95 % confidence level (U.S. DoD, 2020). The combined IRS groundspeed path reaches the cockpit within approximately 0.16 s (Fig. 3, Table 2).

For small lags and slowly varying signals, the display error may be approximated by the product of the lag and the signal’s rate of change (Gracey, 1980). The only additional factor for maintaining equivalence when substituting groundspeed for IAS is the differential display latency:

where GṠ is the rate of change of groundspeed and ΔL = L_GS − L_IAS is the differential lag between the two systems. Near V₁ during normal takeoff acceleration, the Daidzic (2016) energy-balance model gives GṠ ≈ 4 kt/s for a typical reduced-thrust narrowbody departure at maximum takeoff weight. As characterized above, the IRS groundspeed path (≈ 0.16 s) is faster than even the best-case IAS path (≈ 0.45 s for a smart-probe installation), giving a minimum differential |ΔL| ≈ 0.29 s:

This represents the most conservative comparison—the smallest IAS latency against typical IRS latency. For conventional pitot-static installations (IAS latency ≈ 0.75–1.0 s), the differential grows to 0.59–0.84 s and the corresponding speed-reading difference increases to approximately 2.4–3.4 kt. In all cases, groundspeed leads IAS; the GS advantage only increases with longer IAS latencies.

The two-second distance margin in §25.109 already accounts for operational variability in pilot stopping-action times (FAA, 1998); using groundspeed with a comparable or lower latency introduces no additional uncertainty beyond what is already accommodated.

The analysis above applies to the dominant case: IRS-primary groundspeed, for which no lag correction is required. Aircraft equipped with attitude and heading reference system (AHRS) rather than full IRS (principally regional turboprops and business jets; FAA, 2014) typically derive groundspeed from a 1 Hz GNSS receiver, creating a latency of approximately 1.0 s—comparable to the worst-case IAS path. For these installations, a speed correction GSV_1(use) = GSV₁ − GṠ · ΔL_max should be applied; at GṠ ≈ 4 kt/s and ΔL_max ≈ 0.5 s, this amounts to approximately 2 kt.

For IRS-primary or GNSS/IRS-fused installations (Honeywell, 2016), the minimum differential lag is |ΔL| ≈ 0.29 s (smart-probe IAS), with conventional installations showing up to ≈ 0.84 s. Even in the conventional case the resulting speed-reading difference remains below 3.5 kt (Eq. 5), well within the two-second margin of §25.109; no correction is necessary. If groundspeed indications are invalid or unavailable, crews shall revert to existing manufacturer wind shear guidance.

Table 2: Representative latencies for transport-category speed indication systems.

3.3. GSV₁ derivation: the core formula

V₁ is computed and delivered as a calibrated airspeed. To use groundspeed as a decision criterion during wind shear stagnation, the CAS-based V₁ must be mapped to the equivalent groundspeed for the same atmospheric state. The translation rests on two relationships: the correction from CAS to true airspeed (TAS) via compressibility and density-ratio corrections, and the addition of the runway-parallel wind component to obtain groundspeed.

The scalar quantities GS, TAS, and W_∥ used in the equations that follow are the runway-parallel components of the vectors shown in Fig. 4. The relationship between true airspeed and equivalent airspeed follows from density correction:

where equivalent airspeed (EAS) is calibrated airspeed (CAS) corrected for compressibility: EAS = CAS − Δ_comp. Compressibility effects become measurable only above Mach 0.3; at typical takeoff speeds (M ≈ 0.15–0.25), the correction is less than 1 kt. At V₁:

Groundspeed differs from true airspeed by the runway-parallel wind component W_∥, defined as positive for a tailwind and negative for a headwind:

Hence:

At typical V₁ speeds (M ≈ 0.15–0.25), the compressibility correction is less than 1 kt—an order of magnitude smaller than the two-second pilot reaction margin embedded in V₁. For operational use, this term may be omitted. The exact isentropic relation between calibrated airspeed (CAS) and true airspeed (TAS) used in operational performance tools reflects standard pitot–static compressible flow equations. At typical takeoff speeds, simplified density corrections suffice. Thus, for operational use:

The density ratio σ is computed from field conditions:

where p₀ = 1013.25 hectopascals (hPa), T₀ = 288.15 K. Static pressure at field elevation h (standard atmosphere):

Combining all terms:

3.4. Coupled and decoupled physics

Aircraft takeoff performance depends on two physically distinct reference frames: aerodynamic capability (air-relative) and stopping capability (ground-relative). Indicated airspeed governs aerodynamic capability through dynamic pressure:

Thus, IAS is the direct instrument proxy for the dynamic pressure that determines lift coefficient, stall margin, and aerodynamic controllability. Groundspeed governs stopping capability: braking energy E = ½mV²_GS makes stopping distance proportional to the square of groundspeed. Because IAS and GS are linked through a fixed density ratio and the instantaneous wind component, a single IAS-based V₁ serves as a reliable proxy for both aerodynamic capability and ground-referenced stopping performance.

Wind shear disrupts this coupling by rapidly altering the wind component. When a headwind collapses or reverses during the takeoff roll, IAS may stagnate while groundspeed continues to increase. The pre-computed V₁ may no longer provide an adequate real-time stopping cue because the IAS–energy relationship assumed during performance computation is disturbed. The aircraft is not losing aerodynamic capability (IAS remains representative of lift and controllability), but it is gaining ground-relative energy at a rate that was not anticipated when V₁ was computed.

The GSV₁ gate resolves this by expressing the certificated V₁ energy state in ground-referenced terms using the actual atmospheric conditions and the operator's wind policy, preserving Part 25 performance intent while providing a ground-referenced decision threshold when IAS stagnation has been identified.

Because wind shear alters the along-track wind component, the divergence between groundspeed and IAS changes rapidly during a shear encounter. Monitoring this divergence in real time, however, demands sustained crew attention under extreme time pressure. GSV₁ distils the decision into a single pre-computed gate: if the groundspeed reaches a known threshold while IAS has stagnated, the energy state has exceeded the certificated stopping envelope regardless of how the wind is behaving at that instant.

The certificated V₁ may be limited by maximum brake energy (V_MBE), tire speed ratings, or field length rather than purely accelerate-stop distance. These constraints are embedded in the V₁ value and are automatically preserved in GSV₁. The groundspeed translation expresses existing certification limits in ground-referenced terms without bypassing any Part 25 requirement or introducing new performance calculations. The method remains conservative by design: all underlying safety margins are retained.

A special case arises when V₁ is constrained by rotation speed (V_R). Under 14 CFR §25.107, V₁ may not exceed V_R; when field length is generous relative to aircraft weight, the accelerate-stop-limited V₁ would be higher than V_R, so V₁ is capped at V_R.

In these cases, the GSV₁ gate computed from the published V₁ (≈ V_R) is lower than the gate that would result from the unconstrained stopping-limited V₁. The gate therefore triggers a “continue” indication at a groundspeed below the aircraft’s actual stopping capability—the aircraft could safely reject at a higher energy state than the gate implies. This is operationally conservative: it biases toward continuation when ample runway remains, which is the safer default during wind shear.

Operators seeking the full abort envelope may compute GSV₁ from the unconstrained accelerate-stop V₁ (the V₁ that would apply if V_R were not limiting), recovering the additional stopping margin. This refinement is straightforward in EFB tools that already carry the balanced-field and unbalanced-field V₁ values, and has no effect on certification compliance because the underlying performance data are unchanged.

4. Operational decision framework

With the theoretical basis established, we now turn to operational implementation. This section translates the GSV₁ derivation into pre-computable groundspeed gates that crews can brief and reference when airspeed indications stagnate due to wind shear. Two methods are presented—an exact EFB-based calculation and a simplified heuristic for interim use—followed by worked examples, density-effect analysis, and proposed SOP integration.

Historical incidents illustrate the operational reality and allow retrospective application of the GSV₁ method. In February 2020, a Boeing 737-800 departing from East Midlands Airport (AAIB, 2020) during Storm Ciara—the most severe windstorm to affect England and Wales since 2014, with over 25 stations recording gusts exceeding 60 kt (Met Office, 2020)—experienced a 13-knot airspeed loss near V₁ due to wind shear.

The aircraft, with a computed V₁ of 134 knots indicated airspeed (KIAS), encountered significant wind shear with associated downward airspeed trend. The captain, observing the airspeed decay, elected to reject the takeoff five seconds after reaching V₁, bringing the aircraft to a stop with approximately 2000 ft of runway remaining.

The rejected takeoff resulted in thermal damage to the braking system from sustained maximum braking effort. Applying the GSV₁ method retrospectively using the conditions available to the crew at briefing time—previous meteorological aerodrome report (METAR) 209°/40 kt, outside air temperature (OAT) 13 °C, altimeter sub-scale setting (QNH) 981 hPa, field elevation 300 ft, σ ≈ 0.96—the exact GSV₁ computes to approximately 115 kt. The simplified k-factor method yields approximately 100 kt.

The crew's groundspeed at the rejection point was approximately 148 kt—33 kt above the exact gate and 48 kt above the simplified gate—indicating that by the GSV₁ criterion, the aircraft had already far exceeded its certificated V₁ energy state and a continue decision would have been appropriate, consistent with the manufacturer’s subsequent guidance documented in the investigation report (AAIB, 2020).

Notably, the modeled acceleration near V₁ for this 73-tonne aircraft at full takeoff thrust was approximately 5 kt/s (Fig. 6), consistent with the 4–6 kt/s range derived from the Daidzic (2016) energy-balance model (Fig. 1). The higher acceleration compresses the crew’s decision window, reinforcing the need for a pre-briefed groundspeed reference that does not depend on real-time instrument interpretation.

A similar scenario with a different outcome occurred at Perth Airport (ATSB, 2013) in December 2012, where a Boeing 737-838 experienced airspeed stagnation at 134 kt for 3–4 seconds just below its V₁ of 137 KIAS due to unexpected wind conditions that invalidated the nil-wind performance assumptions. The crew continued the takeoff and cleared the runway end at 10 ft radio altitude. For this event—field elevation 67 ft, OAT 37 °C, QNH standard, automatic terminal information service (ATIS) headwind 8 kt—GSV₁ computes to approximately 134 kt (Fig. 7).

At the onset of IAS stagnation, the crew’s groundspeed was approximately 100 kt—well below both the exact GSV₁ gate (134 kt) and the simplified gate (115 kt)—indicating that a rejection remained within the certificated stopping envelope. The crew continued without this reference, clearing the runway end at just 10 ft radio altitude—illustrating both the decision gap the framework addresses and the dangerously thin margins when wind shear is not detected early.

These retrospective analyses demonstrate that the GSV₁ method would have provided the crews with objective, quantitative references precisely when wind shear compromised the IAS-based V₁ framework.

4.1. Exact method: operator-provided GSV₁

Ideally, operators should include GSV₁ directly in takeoff performance data alongside V_1,CAS. The performance calculation software already has all necessary inputs (field elevation, temperature, pressure, wind) and can provide GSV₁ as an additional output with minimal modification. Alternatively, an EFB calculation tool could compute GSV₁ from crew inputs using Eq. 10, which is the foundational exact definition of the gate:

An EFB implementation should evaluate the full expression including the compressibility correction Δ_comp (Eq. 10). Although this correction is negligible at typical takeoff Mach numbers (less than 0.1 kt at sea-level airports, as shown in Section 3.3), it costs nothing to include in a software computation and ensures the gate remains rigorously energy-equivalent across all conditions, including high-elevation airports where the correction grows.

The simplified form (Eq. 11) is reserved for mental arithmetic and interim use without EFB support.

The wind component W_∥ in Eq. 10 uses the same sign convention and value used to compute V₁ (Eq. 9). Because V₁ was calculated under these wind assumptions, the gate must replicate them to represent the same energy state. A headwind reduces the gate; a tailwind raises it. The result is the groundspeed at which the aircraft’s ground-referenced kinetic energy equals the V₁ energy state—neither conservative nor optimistic, but energy-equivalent by construction.

If the performance data specify a required minimum headwind (e.g., “computed for 7 kt headwind minimum”), that headwind value defines W_∥ for the gate calculation.

Note: The term “Groundspeed V₁ Gate” is used throughout because it aligns with terminology familiar to flight crews. However, technically the gate represents an energy-equivalent V₁ condition, meaning the same kinetic-energy state as the certified V₁ under actual atmospheric and wind conditions.

4.2. Simplified method: conservative heuristic

Until the exact GSV₁ is available in operator performance data, crews need an interim criterion that can be quickly computed and briefed. The principle is straightforward: pick a conservative groundspeed gate that is never higher than the exact value. If you reject at or below that number, you're always doing it at or below the energy the airplane was planned to handle for the original V₁. A rule-of-thumb approximation is “V₁ minus 10–20%” under standard and dense air conditions respectively.

This mental-arithmetic approach allows crews to brief the gate in seconds during the takeoff briefing.

where k represents 1/√σ under worst-case dense air conditions (k < 1) and H_required is the minimum headwind from performance data (0 if not specified). The k-factor is pre-selected based on atmospheric conditions, producing a gate that is always at or below the exact value. Wind effects are already embedded in the V₁ performance computation through their influence on both takeoff acceleration and stopping distance.

Unlike the exact method, which uses the full W_∥ to replicate the V₁ energy state precisely, the simplified method adopts a deliberately conservative wind policy: only performance-required headwind is subtracted, and tailwind is not added. When V₁ was computed with tailwind, the published V_1,CAS is already reduced to account for the tailwind’s effect on stopping; by not adding the tailwind back to the groundspeed gate, the simplified threshold sits below the actual V₁ energy state.

This provides an additional safety margin: the crew will reject at lower kinetic energy than V₁ represents, consistent with the interim nature of the simplified method.

Table 3: Simplified k-factor selection for operational use.

The k-factors are derived analytically from the density ratio σ = (p/p₀)(T₀/T). For standard conditions (sea level to 8,000 ft, −25°C to +50°C, QNH 29.50–30.50 inHg), the density ratio spans approximately σ = 0.75–1.15, yielding 1/√σ in the range 0.93–1.15. The standard k = 0.9 therefore guarantees a gate at or below the exact GSV₁ across this entire envelope—a worst-case bound, not an approximation.

The dense air category (k = 0.8) applies when temperature falls below −25°C or QNH exceeds 30.50 inHg, corresponding to σ ≈ 1.15–1.33 where 1/√σ drops below 0.92, making k = 0.9 insufficient.

At sea level with QNH 30.70 inHg and −50°C, σ reaches approximately 1.33—near-maximum density for extreme Arctic operations—and 1/√σ ≈ 0.87, confirming that k = 0.8 provides adequate margin even at this boundary. The conservatism penalty (exact GSV₁ minus simplified GSV₁) has been characterized across the operational envelope via the sensitivity analysis in Fig. 10, showing that the simplified method introduces 5–15 kt of unnecessary margin depending on conditions—a bounded, quantified cost that is eliminated when the exact method is adopted.

4.3. Density effects and worked examples

Atmospheric density directly affects the IAS-to-TAS relationship, varying the GSV₁ threshold by up to 10 kt across the operational envelope. At International Standard Atmosphere (ISA) sea-level conditions (σ = 1.0), GSV₁ equals V_1,CAS. Cold air increases density: at T = −20°C with standard pressure, σ ≈ 1.14, reducing the gate to 0.94 · V_1,CAS — an 8 kt reduction for V_1,CAS = 140.

Pressure effects alone are modest (1 kt at QNH = 30.50 inHg), but cold and high pressure compound: at T = −20 °C and QNH = 30.50 inHg, the gate drops to 0.93 · V_1,CAS, a 10 kt (7.1%) reduction. A crew monitoring only IAS during stagnation could overestimate its energy margin by this amount.

The opposite occurs at elevated airports, where σ < 1 produces GSV₁ > V_1,CAS. This is not a worst-case concern: the higher gate correctly reflects extended stopping distances at altitude, and the certified V₁ already accounts for thin-air deceleration. Figs. 8–10 characterize the full sensitivity landscape across temperature, pressure, and elevation.

The simplified k-factors are chosen to provide a uniformly conservative gate across the operational envelope without requiring operator-specific density calculations during high-workload flight operations. The standard factor k = 0.9 is appropriate for normal operations (typical ambient temperatures between −5°C and 25°C, QNH between 29.60 and 30.30 inHg), covering approximately 90% of commercial operations worldwide.

The dense-air factor k = 0.8 is applied only when either extreme condition is met: (1) temperature below −25°C, which occurs in high-latitude winter operations (Anchorage, Fairbanks, Montreal winter), or (2) QNH exceeding 30.50 inHg, which occurs in strong high-pressure systems (rare but extreme in continental Europe and Asia). These thresholds ensure that the k = 0.9 factor never provides insufficient conservatism while avoiding unnecessary over-conservatism for typical operations.

4.4. Altitude effects

At sea-level airports, the baseline case (h = 0, ISA, QNH 29.92 inHg) yields σ = 1.0 and GSV₁ = V_1,CAS. Cold or high-pressure conditions increase σ above unity, reducing the gate; warm or low-pressure conditions decrease σ, raising it. The k = 0.9 factor covers the range of typical sea-level operations (Miami summer through New York winter); k = 0.8 covers the extreme cold and high-pressure conditions detailed in Figs. 8–10.

At elevated airports, reduced atmospheric pressure dominates. Denver (5,280 ft, ISA) yields σ ≈ 0.86 and GSV₁ ≈ 1.08 · V_1,CAS — an 11-knot increase for V_1,CAS = 140. At La Paz (13,615 ft), σ ≈ 0.66 pushes GSV₁ to roughly 1.23 · V_1,CAS. These higher gates correctly reflect extended stopping distances at altitude; the certified V₁ already accounts for thin-air deceleration, and GSV₁ expresses the same energy state in ground-referenced terms.

4.5. Proposed SOP integration

To embed this method operationally, the following standardized procedures are proposed to integrate into crew training, flight crew operating manuals, and standard operating procedures:

Takeoff briefing (when applicable): “Wind Shear Groundspeed Gate = ___ kt.”

During takeoff roll (when airspeed stagnation is recognized and after verifying engine parameters are normal):

PM: “Wind shear. IAS stagnated. Groundspeed ___ [current reading].”

CA decision: If VGS ≤ gate or aircraft unable to fly: “Abort”

Execution (after “Abort” call): PF rejects using maximum braking and reverse thrust per SOP; PM monitors deceleration, brake temperature, and remaining runway; both pilots prepare for runway overrun contingencies if deceleration is insufficient.

CA decision: If VGS > gate and aircraft able to fly: “Continue”

Execution (after “Continue” call): PF continues with maximum thrust; both pilots follow fleet wind shear rotation and escape procedures; PM monitors airspeed trend, altitude gain, and performance margins.

The standardized callouts are designed to mitigate plan-continuation bias (Orasanu and Davison, 2001) by maintaining shared situation awareness (Endsley, 1995) through a structured PF/PM format. The PM provides the groundspeed reading; the PF makes the abort-or-continue decision, remaining focused on aircraft control rather than instrument scanning or mental calculations.

5. Case application: winter departure scenario

A winter departure scenario illustrates both methods under challenging conditions—cold temperature, high pressure, and a required headwind on a performance-limited runway. The scenario is a constructed example using representative parameters; it is not derived from flight data recorder data or tied to a specific event. Published investigation reports, including the AAIB East Midlands case (AAIB, 2020) and the ATSB Perth event (ATSB, 2013), informed the choice of conditions, but all numerical values are illustrative.

Table 4: Scenario departure conditions.

5.1. Exact calculation

First, compute static pressure at the 2,000-ft field elevation. With QNH = 1032 hPa:

With QNH = 30.47 inHg, the conversion yields 30.47 × 33.8639 = 1032 hPa at sea level, and p(2,000) = 1032 × 0.930 = 959.8 hPa. The density ratio σ combines pressure and temperature effects:

σ = 0.947 × 1.079 = 1.022, indicating air 2.2% denser than standard due to high pressure partially offset by moderate cold (−6°C). The speed-scaling factor is 1/√σ = 1/√1.022 ≈ 0.989. Applying the 7-kt required headwind:

The exact GSV₁ gate is 140 kt—the groundspeed at which the aircraft has the same kinetic-energy state originally certified for V₁ = 149 KIAS under the actual density and wind conditions of this departure.

5.2. Simplified method

The simplified method uses pre-computed k-factors. Current conditions (T = −6°C, QNH = 30.47 inHg) do not exceed the extreme-density thresholds (T < −25°C or QNH > 30.50 inHg), so k = 0.90 applies:

The simplified gate of 127 kt is 13 kt below the exact value (140 kt), representing intentional conservatism. In energy terms, (140/127)² ≈ 1.215, meaning the simplified method requires the aircraft to be 21.5% below its actual V₁ energy state before directing a rejection. This margin constitutes the Risk of Design-induced Missed Abort (RDMA), accepted as an interim measure until operators integrate exact GSV₁ computation into EFB tools.

5.3. Resolution

Table 5: Scenario results comparison.

At the critical event point, a headwind collapse from the briefed 7 kt to an effective tailwind of approximately 17 kt—a 24-kt wind shift exceeding the FAA severe-shear threshold—has produced IAS = 104 kt while VGS = 120 kt. Both methods confirm the aircraft had not yet achieved the ground-referenced energy corresponding to V₁. The IAS-to-groundspeed divergence of 16 kt illustrates the severity of the wind shear encounter: groundspeed was 15% above indicated airspeed due to wind shear effects.

Had the crew been equipped with a pre-briefed groundspeed gate, they would have had an objective, quantitative reference precisely when wind shear compromised the IAS-based V₁ framework.

The 13-kt difference between exact and simplified gates (18% kinetic-energy margin) illustrates why the exact method should be the target for permanent operational adoption, with the simplified method providing interim utility.

6. Implementation and constraints

6.1. Mandatory prerequisites

The groundspeed-based decision criterion is applicable only when three preconditions are satisfied. First, groundspeed indication must be valid: IRS or GNSS groundspeed must be available, reliable, and current, with no flags or warnings indicating sensor failure or quality degradation. Second, the crew must have confirmed a wind shear condition, distinguishing airspeed stagnation from instrument malfunction, systems failure, or engine problems through cross-check with engine parameters—fan speed (N1), fuel flow, and exhaust gas temperature (EGT) all normal—autopilot response, and secondary airspeed sources if available.

Third, adequate directional control must be maintained and the aircraft must remain within the normal control envelope.

Operationally, crews should identify airspeed stagnation as a sustained condition (not transient fluctuation) lasting more than 3 seconds while groundspeed continues to increase normally. If any prerequisite is not met, crews shall revert immediately to existing manufacturer wind shear guidance. The intent is to make the GSV₁ method an enhancement, not a replacement, for existing procedures when all supporting information is available.

Regulatory and certification context: V₁ is determined by accelerate-stop distance calculations under 14 CFR Part 25.107-109. The GSV₁ method does not modify V₁ itself or bypass any Part 25 requirement; it simply provides a ground-referenced interpretation of the same energy state when IAS alone ceases to reflect stopping-distance margin during wind shear.

6.2. Contaminated runways and braking considerations

On contaminated runways (wet, slippery, or snow-covered), groundspeed remains the correct reference for kinetic energy governing stopping distance, though stopping-distance margins are narrower and accelerate-stop performance must be recalculated using contaminated runway friction coefficients. When operating near the groundspeed gate under such conditions with normal acceleration and adequate controllability, crews will likely favor a “continue” bias.

When using the exact method, the gate includes the full wind component W_∥ (Section 4.1), replicating the V₁ energy state regardless of wind direction. When using the simplified method, only performance-required headwind is subtracted and tailwind is omitted, providing additional conservatism (Section 4.2). In either case, manufacturers’ performance data already account for runway surface conditions when computing V₁; the GSV₁ method simply expresses that energy state in ground-referenced terms without altering the underlying performance calculations.

6.3. Risk of Design-induced Missed Abort (RDMA)

The simplified method, due to its intentionally conservative k-factor derivation, introduces a Risk of Design-induced Missed Abort (RDMA). For groundspeeds between the simplified GSV₁ (e.g., 127 kt) and the exact GSV₁ (e.g., 140 kt), the simplified rule directs “continue” even though the aircraft possesses the physical energy margin for a safe abort. This risk is explicitly accepted as an interim measure to mitigate the greater and less-bounded Status-Quo Risk (RSQ) associated with ambiguous high-energy continuation decisions during IAS stagnation.

Because the RDMA is bounded and explicitly quantified — and eliminated entirely when the exact method is used — it represents a more predictable risk profile than the status quo, in which crews have no quantitative reference at all. The simplified method should therefore be treated as an interim SOP, with the EFB-integrated exact method as the preferred target for permanent implementation.

Operators should track the frequency with which departures fall into the RDMA window (GSV_{1(simplified)} < VGS < GSV_1(exact)) as a key performance indicator for migration to the exact method.

6.4. Regulatory and approval framework

Because the method uses only existing certificated data sources (GNSS, IRS, air data) and introduces no hardware or software modifications to type-design systems, the authors contend it constitutes an operational enhancement rather than a type-design change, and that compliance findings to 14 CFR §25.1309 (FAA, 2025b) or EASA CS-25.1309 would not be required. The pitot-static, inertial, and GNSS systems operate entirely within their certificated envelopes; only the operational interpretation of their outputs is reinterpreted.

This classification would need to be confirmed through formal consultation with the relevant certification authority, as the boundary between operational procedures and type-design changes can be subject to regulatory interpretation.

The authors propose that deployment could proceed through three established regulatory channels that have precedent for similar operational enhancements. The feasibility of each pathway would need to be confirmed through consultation with relevant authorities:

(1) SOP revision: Operators incorporate the method into SOPs and Flight Crew Operations Manual (FCOM) through existing principal operations inspector (POI; FAA) or competent-authority (EASA) approval processes. Similar SOP enhancements are approved through these channels annually without triggering certification activity.

(2) EFB integration: The GSV₁ calculation fits naturally into Type A or B EFB performance applications under FAA AC 120-76E (FAA, 2024a), EASA SPA.EFB.100 (EASA, 2025a), and ICAO Doc 10020 (ICAO, 2018). EFB integration requires vendor approval and validation of the calculation logic but does not require aircraft type certification. The simplified method serves as backup when the EFB is inoperative.

(3) Training integration: Scenario-based simulator events under 14 CFR §121.415/419 (FAA) or ORO.FC.120/230 (EASA) would cover wind shear recognition, gate briefing, and decision execution. Many operators already include wind-shear simulator events; integrating the GSV₁ gate requires only SOP and briefing-card updates.

The method is consistent with the crew-interface principles in §25.1302 (FAA, 2013): the pre-briefed gate provides an unambiguous cue, the standardized callouts reduce miscommunication risk, and the engine-parameter prerequisite prevents misapplication to engine-failure scenarios.

6.5. SOP integration examples

During the pre-flight briefing, PF and PM confirm the gate value, the k-factor applied (0.9 or 0.8), and the execution rule: reject if GS ≤ gate or if the aircraft is unable to fly. During the takeoff roll, if the PM observes sustained IAS stagnation (>3 seconds with normal groundspeed increase), the PM calls “Wind shear. Groundspeed ___” and provides updated readings every 2 seconds. The PF decides: abort (if VGS ≤ gate or control is degraded) or continue (if VGS > gate and handling is normal). The expected timeline from detection to decision is 5–10 seconds.

If any prerequisite fails—engine-parameter anomaly, groundspeed display degradation, or unconfirmed shear—the method is abandoned and existing manufacturer guidance takes precedence.

6.6. Implementation roadmap

Table 6: Implementation roadmap: phased deployment of the GSV₁ framework.

A working open-source interactive calculator implementing both methods with live weather integration is freely available and can serve as a reference implementation for EFB development and crew training.

7. Validation pathway

The theoretical framework presented requires systematic empirical validation before operational adoption. Three phases are proposed, with strategic overlap reducing total timeline to 24–30 months. This section outlines the specific data collection, analysis, and human-factors validation needed to establish the safety case and crew performance characteristics.

The validation pathway addresses three questions: (1) How often does airspeed stagnation actually occur in commercial operations? (2) Can crews execute the GSV₁-based decision procedure reliably under operational stress? (3) Does the method provide quantifiable safety benefit?

7.1. Phase 1: flight-data analysis

FOQA or quick-access recorder (QAR) datasets across 100,000+ takeoffs from multiple operators would quantify the industry-wide event rate for IAS stagnation in the high-energy regime (80–100 kt to V₁). Event detection algorithms would identify sequences where IAS rate-of-change falls below 0.5 kt/s for more than 3 seconds while engine thrust (N1 stable within ±2%) and control inputs remain normal—distinguishing true wind shear from sensor degradation or engine problems.

Events would be segmented by aircraft type, geographic region, season, and atmospheric conditions to determine whether IAS stagnation is a universal phenomenon or concentrated in specific environments.

Model validation would compare actual groundspeed at detected IAS-stagnation points with predicted GSV₁ across at least 1,000 independently-selected events, spanning density ratios σ = 0.7–1.2, wind conditions ±15 kt, and field elevations from sea level to 8,000 ft. The dataset should include narrow-body, wide-body, and regional-jet families. Regional jets are of particular interest because PWS inhibition (at 80–100 kt) may prevent automated shear detection early in the takeoff roll.

The target is root-mean-square (RMS) prediction error < 2 kt and correlation coefficient > 0.99 across the operational envelope. A secondary goal is quantifying the business case: event frequency data inform implementation priorities and cost-benefit calculations.

7.2. Phase 2: simulator studies

A minimum of 50 crew pairs, representing a cross-section of seniority, airline size, and aircraft type, would execute realistic wind shear scenarios in full-flight simulators. Scenarios would include headwind collapse, microburst encounters, terrain-induced shear, and frontal passages, with shear onset at early (50 kt), mid-roll (80 kt), and late (100–120 kt) stages. Comparative trials would contrast GSV₁-equipped crews against baseline crews following existing manufacturer guidance.

Recorded measures include recognition time (target < 5 s), decision latency (target < 10 s), stopping-distance margins (target > 15% ASDA), NASA Task Load Index (TLX) workload ratings, and Situation Awareness Rating Technique (SART) scores. Two boundary-case scenarios are essential: (1) engine failure immediately following IAS stagnation, testing whether crews correctly revert to engine-failure procedures, and (2) a controllability-limit scenario where GS exceeds GSV₁ but IAS remains at or below minimum control speed, testing whether crews correctly override the “continue” indication.

Success criteria include 95%+ correct decision rate, mean decision latency < 10 s, 100% correct response in boundary cases, and crew satisfaction > 3.5/5.

7.3. Phase 3: operational validation

Limited trials with designated line-evaluation crews would involve briefing GSV₁ gates on 50–100 takeoffs in wind-shear-prone environments (tropical thunderstorm regions, complex terrain, high-altitude airports). Documentation would capture ease of SOP integration, crew decision confidence (via post-flight Likert-scale surveys), brake temperatures and stopping margins, and operational anomalies. Success criteria include 90%+ crew satisfaction, no adverse safety events, and clean SOP integration.

Table 7: Validation timeline with strategic phase overlap.

Results from all three phases would be compiled into a formal safety case for FAA/EASA operator approval. FOQA analysis must be substantially complete before Phase 3, since regulatory justification requires event-frequency data. Conservative planning should budget 30–36 months to accommodate data collection delays and regulatory review cycles.

8. Discussion

This paper addresses a recognized gap in takeoff wind shear guidance: the absence of a quantitative, ground-referenced decision threshold when indicated airspeed stagnates during the high-energy takeoff regime. The relationship between groundspeed and stopping energy is well established in aeronautical engineering, but translating it into a cockpit-usable abort criterion—without recomputing the manufacturer’s certified stopping performance—had not been attempted.

Why this gap persisted for roughly four decades after the JAWS-era wind shear research is worth considering. Three factors likely contributed. First, the success of ground-based detection—Terminal Doppler Weather Radar (TDWR) and LLWAS—and onboard reactive/predictive systems in reducing approach-phase accidents shifted research attention away from the takeoff roll, where encounters are rarer and less well documented.

Second, the certification framework anchors V₁ to indicated airspeed; translating it to groundspeed requires density-ratio arithmetic that, before EFB integration became routine, was impractical for line crews. Third, the rarity of documented takeoff-roll wind shear events meant the problem attracted less institutional urgency than higher-frequency hazards.

The two-tier approach balances precision against immediate usability. The exact method, suitable for EFB integration, provides the correct energy-equivalent threshold with no conservatism penalty. The simplified method trades precision for deployability, introducing a deliberately bounded Risk of Design-induced Missed Abort (RDMA) that we accept as an interim measure.

The RDMA does introduce a narrow risk of missed abort opportunities—for example, groundspeeds between 127 kt and 140 kt in the worked scenario—but it is bounded and predictable. The corresponding risk under current practice, where crews have no quantitative reference during IAS stagnation, is neither bounded nor quantified.

The framework’s reliance on existing groundspeed displays and certificated data is both its primary strength and a recognized limitation. It can be deployed through routine SOP revision and EFB authorization without aircraft modification. However, aircraft equipped with AHRS rather than full IRS may have degraded groundspeed quality; operators with mixed avionics architectures will need to address this on a fleet-by-fleet basis (Section 3.2).

The SOP integration—PF/PM callouts with a pre-briefed gate—is intended to counter the plan-continuation bias identified by Orasanu and Davison (2001) and the interpretive variability documented by Fischer et al. (2008). By converting a subjective runway-remaining assessment into a binary comparison (current groundspeed versus pre-briefed gate), the procedure aims to reduce cognitive load at the decision point, consistent with crew resource management (CRM) principles and the error-reduction objectives of 14 Code of Federal Regulations (CFR) §25.1302 (FAA, 2013).

Whether this translates into measurable workload reduction and better decisions is an empirical question—one the simulator studies in Section 7.2 are designed to answer.

When the crew elects to continue (GS > GSV₁), the takeoff transitions into the manufacturer’s published wind shear escape maneuver. The GSV₁ framework addresses only the abort-or-continue decision; operators should ensure their SOP explicitly sequences the GSV₁ decision before the escape procedure.

Several limitations bear emphasis. The framework is a conceptual and operational proposal that has not yet been validated empirically. It applies only to confirmed wind shear conditions with valid groundspeed indications; it does not cover simultaneous system failures, engine failure, crew incapacitation, or loss of groundspeed data. We have not subjected the derivation to large-scale flight data analysis or to human-factors simulator validation. Procedures that appear sound on paper may fail in practice—crew adoption, training effectiveness, and real-world decision timing cannot be assumed.

The validation pathway outlined in Section 7 is therefore not optional. Operational adoption without empirical evidence of crew performance under realistic conditions would be premature.

Because the V₁ already embodies all certificated performance margins, including those for accelerate-stop distance, minimum control speed, brake energy, and tire speed limits, the GSV₁ transformation introduces no new performance margins and bypasses no certified limit. The aircraft's ability to stop is unchanged; only the reference frame for the decision cue is shifted from air-relative (IAS) to ground-relative (GS) when wind shear has decoupled IAS from the aircraft's ground-referenced energy state.

Future work falls into three areas: FOQA-based frequency analysis to establish operational relevance, simulator studies to provide quantitative safety-benefit evidence, and longer-term integration with next-generation flight management system (FMS) and synthetic vision displays. Because the derivation rests on the ICAO Standard Atmosphere and certification principles common to 14 CFR Part 25 and EASA CS-25, the method is applicable to any operator whose aircraft is certificated under either framework.

Finally, the F-factor hazard index already certified on transport aircraft under FAA Technical Standard Order (TSO)-C117b (FAA, 2018) provides a natural complement to the GSV₁ framework. Existing onboard reactive wind shear systems detect the presence and severity of shear through the F-factor; GSV₁ supplies the missing decision layer—the quantitative abort/continue threshold—that detection alone cannot provide. As Fig. 5 illustrates, the F-factor confirms the energy loss rate during the encounter, while the GSV₁ gate provides the crew with a pre-briefed groundspeed reference for acting on that information.

9. Conclusions

Airspeed governs whether the aircraft can fly; groundspeed governs whether it can stop. During wind shear on the takeoff roll, it is the ground-referenced kinetic energy—not the indicated airspeed—that determines stopping distance. We have derived a physics-based framework for expressing the certificated V₁ decision speed in ground-referenced terms, giving flight crews a briefable, objective threshold that preserves Part 25 certification intent without requiring hardware modification, new certification activity, or regulatory amendment.

The framework provides two complementary tools: an exact GSV₁ calculation suitable for EFB integration, and a conservative simplified heuristic for interim use through mental arithmetic. Both complement—rather than replace—manufacturer wind shear guidance and existing rejected-takeoff doctrine.

This paper completes the theoretical foundation. Operational adoption requires the validation work described in Section 7: FOQA analysis to quantify IAS stagnation frequency, simulator studies to verify crew performance under stress, and operational trials to confirm SOP integration. Whether the theoretical case translates into measurably safer operations depends on that work.

No datasets were generated or analyzed during the current study. The framework is derived from publicly available atmospheric models and published certification standards.

During the preparation of this work, the author used Claude (Anthropic) to assist with manuscript formatting and editorial review. After using this tool, the author reviewed and edited the content as needed and takes full responsibility for the content of the publication.

References