GPWS - Revision history

codex: Ticket 1734: update verified harness count after shared scheduling regressions

2026-10-14T17:37:35Z

Ticket 1734: update verified harness count after shared scheduling regressions

← Older revision		Revision as of 17:37, 14 October 2026
Line 235:		Line 235:
	[[File:GPWS-mode7-Rise-2026-sampled.png\|thumb\|center\|1000px\|Corrected Rise Mode 7: signed headwind change over one second versus local-vertical wind. Purple identifies the retained numerical approximation, not a manufacturer escape-performance specification.]]		[[File:GPWS-mode7-Rise-2026-sampled.png\|thumb\|center\|1000px\|Corrected Rise Mode 7: signed headwind change over one second versus local-vertical wind. Purple identifies the retained numerical approximation, not a manufacturer escape-performance specification.]]

	'''Verification:''' the production GPWS/VMU harness passed ~~805~~ checks in both Win32 Debug and optimized Release, including all 20 combinations of 15/30/60/144/240 FPS and 1/5/20/60 Hz sensor updates. The linear replay produced identical shear rates and expected warning/recovery/caution states; variable 7–100 ms frames differed by less than 0.000008 knots/second. Sensor rate still determines observation latency. Hover headwind/tailwind reversals across several headings, turn compensation, invalid/stale data, reset paths, orbit/re-entry and queued-audio expiry are covered. These tests establish implementation behavior, not manufacturer certification.		'''Verification:''' the production GPWS/VMU harness passed 889 checks in both Win32 Debug and optimized Release, including all 20 combinations of 15/30/60/144/240 FPS and 1/5/20/60 Hz sensor updates. The linear replay produced identical shear rates and expected warning/recovery/caution states; variable 7–100 ms frames differed by less than 0.000008 knots/second. Sensor rate still determines observation latency. Hover headwind/tailwind reversals across several headings, turn compensation, invalid/stale data, reset paths, orbit/re-entry and queued-audio expiry are covered. The shared-scheduler follow-up also covers 1/7/50-module timing, separate GPWS/VMU turns and complete VMU warm-up speech. These tests establish implementation behavior, not manufacturer certification.

	== Audio behavior and self-test ==		== Audio behavior and self-test ==

codex: Tickets 1196/1734: document shared module scheduling as a purple Rise adaptation

2026-10-14T17:35:55Z

Tickets 1196/1734: document shared module scheduling as a purple Rise adaptation

← Older revision		Revision as of 17:35, 14 October 2026
Line 54:		Line 54:
	* Only received geometry is known. There is no certified worldwide terrain/obstacle database or airport-specific modulation catalog. Unknown data is not assumed to be flat or safe.		* Only received geometry is known. There is no certified worldwide terrain/obstacle database or airport-specific modulation catalog. Unknown data is not assumed to be flat or safe.
	* These are Rise advisory margins, not a reproduction of proprietary Honeywell coefficients or a guaranteed escape-maneuver calculation.		* These are Rise advisory margins, not a reproduction of proprietary Honeywell coefficients or a guaranteed escape-maneuver calculation.
			</div>


			<div style="background:#f4ecf8;color:#38263f;border-left:6px solid #753a91;padding:12px;">
			'''Rise adaptation — shared module scheduling.''' Rise runs '''one module per enabled simulation frame''', rotating through the registered modules. Each module receives the actual elapsed time since its previous turn. GPWS evaluates its alerts and performs an eligible terrain scan on that turn; it has no separate 5 Hz target or timer-driven catch-up calls. This is a simulator CPU-budget choice, not a stated EGPWS hardware update rate.

			With the current '''seven modules''', each runs about '''8.6 Hz at 60 FPS, 4.3 Hz at 30 FPS, and 2.1 Hz at 15 FPS'''. The rate is FPS divided by module count, so additional modules or lower FPS increase response latency. Physics and cockpit drawing retain their existing cadence; displays draw the latest available module results between turns. Elapsed-time timers remain time-based. Existing internal intervals still apply: TCAS has its own analysis timer, and CAS rotates its message categories over multiple CAS turns.

			This spreads module work across frames; it is '''not a guaranteed FPS improvement'''. At 60 FPS, scanning terrain on each of seven module turns is more frequent than the former nominal 5 Hz terrain throttle. Flight testing must check CPU cost and alert/callout latency together, including ground, hover, approaches, fast near-ground flight, orbit/re-entry and uneven frame times. Existing invalid/stale-data rules remain; very slow scheduling cannot be treated as fresh sensor coverage.
	</div>		</div>

codex: Ticket 1196: clarify hover wind direction; 805 Debug/Release regression checks

2026-10-14T17:09:17Z

Ticket 1196: clarify hover wind direction; 805 Debug/Release regression checks

← Older revision		Revision as of 17:09, 14 October 2026
Line 217:		Line 217:
	Wind change is measured over a rolling '''one-second interval using sensor timestamps''', independently of rendering frame rate and the map wind readout. Turning in steady wind does not create artificial shear. Unchanged samples retain their result; input older than two seconds is discarded. Reset or recovered input starts a fresh history: horizontal change needs one second, while vertical-wind protection is immediate.		Wind change is measured over a rolling '''one-second interval using sensor timestamps''', independently of rendering frame rate and the map wind readout. Turning in steady wind does not create artificial shear. Unchanged samples retain their result; input older than two seconds is discarded. Reset or recovered input starts a fresh history: horizontal change needs one second, while vertical-wind protection is immediate.

	'''Operating band: 10–1,500 ft AGL''', powered and airborne, with valid inputs and hazard inhibit off. Rise protects APN and ACL flight, including level flight and VTOL/hover; this is broader than the reference aircraft's takeoff/approach phases. Low IAS does not disable it, and it never divides by airspeed. Ground, vehicle/simulator transitions, invalid inputs and leaving the band clear the history. Re-entry into the band re-arms it. The separate bank-advisory spaceflight exclusion does not suppress fast near-ground windshear protection.		'''Operating band: 10–1,500 ft AGL''', powered and airborne, with valid inputs and hazard inhibit off. Rise protects APN and ACL flight, including level flight and VTOL/hover; this is broader than the reference aircraft's takeoff/approach phases. Low IAS does not disable it, and it never divides by airspeed. With no ground track, it uses the aircraft's horizontal nose direction; if that also cannot be defined, vertical-wind protection remains available. Ground, vehicle/simulator transitions, invalid inputs and leaving the band clear the history. Re-entry into the band re-arms it. The separate bank-advisory spaceflight exclusion does not suppress fast near-ground windshear protection.

	'''Remaining approximation:''' let H be the one-second headwind change in knots/second (positive for increasing headwind), and W the local updraft in feet/minute. Rise retains '''S = W + 750 H''': below −1,750 warns; above +1,750 cautions. These coefficients are not Honeywell's aircraft-performance-dependent algorithm or a validated Vieneo escape model. '''Purple marks this approximation; Mode 7 itself is a real EGPWS function.'''		'''Remaining approximation:''' let H be the one-second headwind change in knots/second (positive for increasing headwind), and W the local updraft in feet/minute. Rise retains '''S = W + 750 H''': below −1,750 warns; above +1,750 cautions. These coefficients are not Honeywell's aircraft-performance-dependent algorithm or a validated Vieneo escape model. '''Purple marks this approximation; Mode 7 itself is a real EGPWS function.'''
Line 226:		Line 226:
	[[File:GPWS-mode7-Rise-2026-sampled.png\|thumb\|center\|1000px\|Corrected Rise Mode 7: signed headwind change over one second versus local-vertical wind. Purple identifies the retained numerical approximation, not a manufacturer escape-performance specification.]]		[[File:GPWS-mode7-Rise-2026-sampled.png\|thumb\|center\|1000px\|Corrected Rise Mode 7: signed headwind change over one second versus local-vertical wind. Purple identifies the retained numerical approximation, not a manufacturer escape-performance specification.]]

	'''Verification:''' the production GPWS/VMU harness passed ~~796~~ checks, including all 20 combinations of 15/30/60/144/240 FPS and 1/5/20/60 Hz sensor updates. The linear replay produced identical shear rates and expected warning/recovery/caution states; variable 7–100 ms frames differed by less than 0.000008 knots/second. Sensor rate still determines observation latency. Hover, turn compensation, invalid/stale data, reset paths, orbit/re-entry and queued-audio expiry are covered. These tests establish implementation behavior, not manufacturer certification.		'''Verification:''' the production GPWS/VMU harness passed 805 checks in both Win32 Debug and optimized Release, including all 20 combinations of 15/30/60/144/240 FPS and 1/5/20/60 Hz sensor updates. The linear replay produced identical shear rates and expected warning/recovery/caution states; variable 7–100 ms frames differed by less than 0.000008 knots/second. Sensor rate still determines observation latency. Hover headwind/tailwind reversals across several headings, turn compensation, invalid/stale data, reset paths, orbit/re-entry and queued-audio expiry are covered. These tests establish implementation behavior, not manufacturer certification.

	== Audio behavior and self-test ==		== Audio behavior and self-test ==

codex: Ticket 1196: document corrected reactive windshear inputs, local vertical/gusts, sample timing, operating band and frame-rate verification; replace Mode 7 graph.

2026-10-14T15:36:23Z

Ticket 1196: document corrected reactive windshear inputs, local vertical/gusts, sample timing, operating band and frame-rate verification; replace Mode 7 graph.

← Older revision		Revision as of 15:36, 14 October 2026
Line 213:		Line 213:

	<div style="background:#f4ecf8;color:#38263f;border-left:6px solid #753a91;padding:12px;">		<div style="background:#f4ecf8;color:#38263f;border-left:6px solid #753a91;padding:12px;">
	'''Rise ~~approximation~~ — ~~current Mode 7 algorithm~~.''' ~~Rise~~'~~s existing caution/warning logic uses~~ change in wind-speed '''~~magnitude~~''' ~~per elapsed~~ second ~~and~~ vertical wind, with valid inputs ~~in atmospheric~~ flight ~~mode up to 1~~,~~500 ft AGL. This~~ is ~~not~~ the ~~real unit~~'s ~~headwind~~-~~component/performance algorithm or an exact reproduction of its flight~~-~~phase gates~~. The ~~retained~~ coefficients ~~have~~ not ~~been validated for a~~ Honeywell ~~installation~~ or Vieneo escape ~~performance~~. '''Purple ~~identifies that numerical~~ approximation; ~~windshear~~ itself is ~~not~~ a ~~Rise-only extension~~.''' ~~The earlier “not currently implemented” label was also inaccurate.~~		'''Rise implementation — corrected wind inputs (14 October 2026).''' The detector now uses '''signed headwind change''' and '''local-vertical wind''', including the gusts applied by flight physics. A headwind becoming a tailwind is no longer hidden by equal wind-speed magnitudes. Global Y is no longer treated as local up.

			Wind change is measured over a rolling '''one-second interval using sensor timestamps''', independently of rendering frame rate and the map wind readout. Turning in steady wind does not create artificial shear. Unchanged samples retain their result; input older than two seconds is discarded. Reset or recovered input starts a fresh history: horizontal change needs one second, while vertical-wind protection is immediate.

			'''Operating band: 10–1,500 ft AGL''', powered and airborne, with valid inputs and hazard inhibit off. Rise protects APN and ACL flight, including level flight and VTOL/hover; this is broader than the reference aircraft's takeoff/approach phases. Low IAS does not disable it, and it never divides by airspeed. Ground, vehicle/simulator transitions, invalid inputs and leaving the band clear the history. Re-entry into the band re-arms it. The separate bank-advisory spaceflight exclusion does not suppress fast near-ground windshear protection.

			'''Remaining approximation:''' let H be the one-second headwind change in knots/second (positive for increasing headwind), and W the local updraft in feet/minute. Rise retains '''S = W + 750 H''': below −1,750 warns; above +1,750 cautions. These coefficients are not Honeywell's aircraft-performance-dependent algorithm or a validated Vieneo escape model. '''Purple marks this approximation; Mode 7 itself is a real EGPWS function.'''
	</div>		</div>

	[[File:GPWS-mode7-Rise-2026-~~corrected~~.png\|thumb\|center\|1000px\|Mode 7 ~~is a real EGPWS function~~. Purple ~~shows Rise's current~~ numerical approximation, not a manufacturer ~~or Vieneo~~ escape-performance specification.]]		All alerts continue through the existing command bus and VMU, with complete phrases and stale queued-warning removal. This update changes the measured inputs and their timing; it does not add predictive radar, retune Vieneo's atmosphere, or change the existing four-second windshear repeat eligibility.

			[[File:GPWS-mode7-Rise-2026-sampled.png\|thumb\|center\|1000px\|Corrected Rise Mode 7: signed headwind change over one second versus local-vertical wind. Purple identifies the retained numerical approximation, not a manufacturer escape-performance specification.]]

			'''Verification:''' the production GPWS/VMU harness passed 796 checks, including all 20 combinations of 15/30/60/144/240 FPS and 1/5/20/60 Hz sensor updates. The linear replay produced identical shear rates and expected warning/recovery/caution states; variable 7–100 ms frames differed by less than 0.000008 knots/second. Sensor rate still determines observation latency. Hover, turn compensation, invalid/stale data, reset paths, orbit/re-entry and queued-audio expiry are covered. These tests establish implementation behavior, not manufacturer certification.

	== Audio behavior and self-test ==		== Audio behavior and self-test ==

codex: Correct Mode 7 scope: reactive windshear is a real EGPWS/CRJ function; purple marks Rise algorithm approximation. Add primary references and corrected graph. Ticket 1196.

2026-10-14T15:08:59Z

Correct Mode 7 scope: reactive windshear is a real EGPWS/CRJ function; purple marks Rise algorithm approximation. Add primary references and corrected graph. Ticket 1196.

← Older revision		Revision as of 15:08, 14 October 2026
Line 1:		Line 1:
	'''GPWS''' (Ground Proximity Warning System, pronounced ''jip-wiz'') warns the crew about unsafe descent, terrain closure, clearance and approach conditions. Rise also provides predictive terrain and obstacle awareness using the terrain and city/colony geometry received by the client.		'''GPWS''' (Ground Proximity Warning System, pronounced ''jip-wiz'') warns the crew about unsafe descent, terrain closure, clearance and approach conditions. Rise also provides predictive terrain and obstacle awareness using the terrain and city/colony geometry received by the client.

	This page describes the '''October 2026 GPWS update''', checked against the client on 14 October 2026. Older clients may behave differently. The comparison reference is the Honeywell '''MK VI & MK VIII EGPWS Pilot Guide, 060-4314-000, Rev C, May 2004''', primarily its enabled jet installation. Its optional features and installation choices are not universal to every real EGPWS.		This page describes the '''October 2026 GPWS update''', checked against the client on 14 October 2026. Older clients may behave differently. The comparison reference is the Honeywell '''MK VI & MK VIII EGPWS Pilot Guide, 060-4314-000, Rev C, May 2004''', primarily its enabled jet installation. Its optional features and installation choices are not universal to every real EGPWS. Mode 7 additionally references the Honeywell MK V/VII guide and Bombardier CRJ documentation below; the absence of windshear from the supplied six-mode guide does not exclude it from other EGPWS installations.

	{\| class="wikitable" style="width:100%;"		{\| class="wikitable" style="width:100%;"
Line 202:		Line 202:
	== Additional clearance and windshear functions ==		== Additional clearance and windshear functions ==
	'''Terrain Clearance Floor / Runway Field Clearance Floor:''' separate “Too low terrain” protection compares radio clearance and geometric height above received runway elevation with distance-dependent floors. It remains independent of landing configuration and the predictive runway allowance. Position-integrity settings affect the inner bias. Only received runway data is available; the client does not synthesize a worldwide airport database.		'''Terrain Clearance Floor / Runway Field Clearance Floor:''' separate “Too low terrain” protection compares radio clearance and geometric height above received runway elevation with distance-dependent floors. It remains independent of landing configuration and the predictive runway allowance. Position-integrity settings affect the inner bias. Only received runway data is available; the client does not synthesize a worldwide airport database.

			=== Mode 7 — Reactive windshear ===
			<div style="background:#eaf3fa;color:#174f78;border-left:6px solid #17639c;padding:12px;">
			'''Documented aircraft function.''' Mode 7 reactive windshear is part of equipped EGPWS installations, including the CRJ. Bombardier's CRJ100/200 Navigation chapter places monitoring during takeoff and final approach at 10–1,500 ft radio altitude. A warning produces a siren, the triple WINDSHEAR announcement and a red PFD indication, with flight-director escape guidance. Headwind/updraft encounters can produce an amber indication. [https://www.jettairx.com.br/backup/wp-content/uploads/2015/07/Bombardier_CRJ_200-Navigation_System.pdf#page=55 Bombardier: Mode 7]
			</div>

			The supplied '''MK VI/VIII''' guide describes six basic modes; that is not the scope of every EGPWS. Honeywell's '''MK V/VII''' guide explicitly documents Mode 7 for installations with the required inputs and enabled algorithms. It considers headwind changes and vertical wind; warning thresholds also account for aircraft performance and flight conditions. [https://data.ntsb.gov/Docket/Document/docBLOB?FileExtension=.PDF&FileName=EGPWS+Pilot+Guide-Master.PDF&ID=40281309#page=25 Honeywell: Mode 7]

			'''Reactive''' detection responds to the aircraft's encounter. '''Predictive''' windshear is a separate forward-looking weather-radar capability that can warn before entry; it should not be inferred from the presence of Mode 7. [https://www.honeywellaerospace.com/us/en/insights/articles/radar-corner-follow-up-understanding-windshear-detection-systems Honeywell: forward-looking windshear radar]

	<div style="background:#f4ecf8;color:#38263f;border-left:6px solid #753a91;padding:12px;">		<div style="background:#f4ecf8;color:#38263f;border-left:6px solid #753a91;padding:12px;">
	'''Rise ~~extension~~ — Mode 7 ~~windshear~~.''' ~~The~~ existing ~~windshear~~ caution/warning logic ~~is implemented, using~~ wind-speed ~~change~~ per elapsed second and vertical wind in atmospheric flight up to 1,500 ft AGL. It is ~~beyond~~ the ~~supplied six~~-~~mode MK VI~~/~~VIII guide~~. ~~Its~~ retained coefficients have not been ~~established as~~ a Honeywell or Vieneo ~~aircraft~~ escape-~~performance model~~. The ~~old~~ “not currently implemented” label was inaccurate.		'''Rise approximation — current Mode 7 algorithm.''' Rise's existing caution/warning logic uses change in wind-speed '''magnitude''' per elapsed second and vertical wind, with valid inputs in atmospheric flight mode up to 1,500 ft AGL. This is not the real unit's headwind-component/performance algorithm or an exact reproduction of its flight-phase gates. The retained coefficients have not been validated for a Honeywell installation or Vieneo escape performance. '''Purple identifies that numerical approximation; windshear itself is not a Rise-only extension.''' The earlier “not currently implemented” label was also inaccurate.
	</div>		</div>

	[[File:GPWS-mode7-Rise-2026.png\|thumb\|center\|1000px\|Mode 7 ~~retained Rise windshear model~~. Purple ~~identifies a~~ Rise ~~extension~~, not a manufacturer or Vieneo escape-performance specification.]]		[[File:GPWS-mode7-Rise-2026-corrected.png\|thumb\|center\|1000px\|Mode 7 is a real EGPWS function. Purple shows Rise's current numerical approximation, not a manufacturer or Vieneo escape-performance specification.]]

	== Audio behavior and self-test ==		== Audio behavior and self-test ==
Line 222:		Line 231:
	== Reference and scope ==		== Reference and scope ==
	* Honeywell, ''MK VI & MK VIII EGPWS Pilot Guide'', 060-4314-000, Rev C, May 2004: modes pp.10–25; clearance floors pp.26–28; predictive awareness pp.29–30; display pp.31–37; priority p.40; controls/testing pp.42–55.		* Honeywell, ''MK VI & MK VIII EGPWS Pilot Guide'', 060-4314-000, Rev C, May 2004: modes pp.10–25; clearance floors pp.26–28; predictive awareness pp.29–30; display pp.31–37; priority p.40; controls/testing pp.42–55.
			* Honeywell, [https://data.ntsb.gov/Docket/Document/docBLOB?FileExtension=.PDF&FileName=EGPWS+Pilot+Guide-Master.PDF&ID=40281309 MK V & MK VII EGPWS Pilot Guide], 060-4241-000: Mode 7 reactive windshear (PDF pages 25–26).
			* Bombardier, [https://www.jettairx.com.br/backup/wp-content/uploads/2015/07/Bombardier_CRJ_200-Navigation_System.pdf#page=55 Canadair Regional Jet 100/200 — Navigation], Ground Proximity Warning System, Mode 7, PDF page 55. Aircraft installation reference; not a claim that every CRJ variant has identical equipment.
	* Current Rise implementation: GPWS, terrain awareness, VMU, CAS and shared moving-map logic; ticket [https://jira.risetvp.com/view.php?id=1196 1196].		* Current Rise implementation: GPWS, terrain awareness, VMU, CAS and shared moving-map logic; ticket [https://jira.risetvp.com/view.php?id=1196 1196].
	* This page describes implemented behavior and identified approximations. Passing regression tests does not establish complete conformity with a manufacturer's installation, or turn an aircraft manual into a spaceflight specification.		* This page describes implemented behavior and identified approximations. Passing regression tests does not establish complete conformity with a manufacturer's installation, or turn an aircraft manual into a spaceflight specification.

	[[Category:Avionics]]		[[Category:Avionics]]

codex: Restore visual mode coverage with eight updated GPWS graphs: Modes 1, 2, 3, 4A/B/C, 5 and 7; label documented limits versus Rise approximations.

2026-10-14T15:00:26Z

Restore visual mode coverage with eight updated GPWS graphs: Modes 1, 2, 3, 4A/B/C, 5 and 7; label documented limits versus Rise approximations.

← Older revision		Revision as of 15:00, 14 October 2026
Line 101:		Line 101:
	== Reactive GPWS modes ==		== Reactive GPWS modes ==
	The modes below use current aircraft state and measured clearance/closure. They remain distinct from predictive terrain/obstacle awareness. Their spoken alerts pass through the same voice management system.		The modes below use current aircraft state and measured clearance/closure. They remain distinct from predictive terrain/obstacle awareness. Their spoken alerts pass through the same voice management system.

			The replacement graphs show each mode in isolation; power, airborne state, valid inputs, configuration, inhibits and alert priority still apply. Blue identifies documented jet limits used by Rise. Purple identifies numerical Rise approximations or explicitly labeled illustrative inputs. Plot shading is a documentation aid, not the cockpit terrain-color legend. Click a graph for the full-resolution image. Height axes use feet to match the guide (1 ft = 0.3048 m).

	=== Mode 1 — Excessive descent rate ===		=== Mode 1 — Excessive descent rate ===
			[[File:GPWS-mode1-Rise-2026.png\|thumb\|center\|1000px\|Mode 1 default Rise envelope. Purple marks the numerical Rise approximation; this plot excludes steep-approach and above-glideslope capture biases.]]

	'''Aircraft reference:''' “Sink rate” warns of excessive descent; deeper penetration produces “Whoop whoop, pull up.” It does not require a particular gear/flap configuration.		'''Aircraft reference:''' “Sink rate” warns of excessive descent; deeper penetration produces “Whoop whoop, pull up.” It does not require a particular gear/flap configuration.

Line 109:		Line 113:

	=== Mode 2 — Excessive terrain closure ===		=== Mode 2 — Excessive terrain closure ===
			[[File:GPWS-mode2-Rise-2026.png\|thumb\|center\|1000px\|Mode 2A/2B reactive closure envelopes. Purple: current Rise curves. Blue dashed line: the documented available-TAD cap. The fully configured Mode 2B case suppresses Pull Up.]]

	'''Aircraft reference:''' rapid closure produces “Terrain, terrain” and, when appropriate, “Whoop whoop, pull up.” Mode 2B reduces nuisance alerts in landing/airport conditions. Fully configured landing uses the single “Terrain” warning instead of Pull Up.		'''Aircraft reference:''' rapid closure produces “Terrain, terrain” and, when appropriate, “Whoop whoop, pull up.” Mode 2B reduces nuisance alerts in landing/airport conditions. Fully configured landing uses the single “Terrain” warning instead of Pull Up.

Line 115:		Line 121:

	=== Mode 3 — Altitude loss after takeoff or low go-around ===		=== Mode 3 — Altitude loss after takeoff or low go-around ===
			[[File:GPWS-mode3-Rise-2026.png\|thumb\|center\|1000px\|Mode 3 current Rise altitude-loss threshold, plotted in purple because the guide does not supply a numerical jet curve to reproduce.]]

	“Don't sink” responds to loss of '''geometric altitude''', rather than mistaking rising terrain beneath a climbing vehicle for a descent. It arms after takeoff or a low go-around, applies when not fully configured for landing, and recovers with positive climb.		“Don't sink” responds to loss of '''geometric altitude''', rather than mistaking rising terrain beneath a climbing vehicle for a descent. It arms after takeoff or a low go-around, applies when not fully configured for landing, and recovers with positive climb.
	<div style="background:#f4ecf8;border-left:6px solid #753a91;padding:10px;color:#38263f;">'''Rise approximation:''' the retained jet loss threshold is 8 − 3h meters, where h is radio altitude in kilometers; the takeoff phase ends above 1,500 ft AGL. These are Rise coefficients, not the old wiki's “10% of AGL” rule or a claimed numerical Honeywell jet specification.</div>		<div style="background:#f4ecf8;border-left:6px solid #753a91;padding:10px;color:#38263f;">'''Rise approximation:''' the retained jet loss threshold is 8 − 3h meters, where h is radio altitude in kilometers; the takeoff phase ends above 1,500 ft AGL. These are Rise coefficients, not the old wiki's “10% of AGL” rule or a claimed numerical Honeywell jet specification.</div>
Line 130:		Line 138:
	\|}		\|}
	Available terrain awareness removes the Mode 4 speed expansion: 4A/4C retain a 500 ft cap and 4B a 245 ft cap. A/B operate from 50 ft AGL and include level flight; descent is not required. Aircraft-specific overflight desensitization and every installation option are not reproduced.		Available terrain awareness removes the Mode 4 speed expansion: 4A/4C retain a 500 ft cap and 4B a 245 ft cap. A/B operate from 50 ft AGL and include level flight; descent is not required. Aircraft-specific overflight desensitization and every installation option are not reproduced.



			[[File:GPWS-mode4a-Rise-2026.png\|thumb\|center\|1000px\|Mode 4A: gear-up clearance floor. Blue shows the documented jet speed ramp used in Rise; the dashed line shows the available-terrain-awareness cap.]]

			[[File:GPWS-mode4b-Rise-2026.png\|thumb\|center\|1000px\|Mode 4B: gear-down, flaps-not-landing clearance floor, including the available-terrain-awareness cap.]]

			[[File:GPWS-mode4c-Rise-2026.png\|thumb\|center\|1000px\|Mode 4C: blue clearance-history floor with a purple illustrative flight path. This example shows why the floor does not fall when the aircraft begins descending; it is not measured flight data.]]

	=== Mode 5 — Below glideslope ===		=== Mode 5 — Below glideslope ===
			[[File:GPWS-mode5-Rise-2026.png\|thumb\|center\|1000px\|Mode 5 for a qualifying approach descending at least 500 ft/min. Blue: nominal dot thresholds. Purple: the current Rise regions and near-ground approximation. The upper height limit reduces toward 500 ft in level flight.]]

	A valid front-course ILS can qualify a '''hand-flown''' approach; Autoflyte G/S capture is not required. The upper radio-height limit varies from 500 to 1,000 ft with descent rate. The soft region begins at about 1.3 dots low; the hard region is below 300 ft and at least about two dots low. Both become less sensitive very near the ground, and no Mode 5 alert occurs below 50 ft.		A valid front-course ILS can qualify a '''hand-flown''' approach; Autoflyte G/S capture is not required. The upper radio-height limit varies from 500 to 1,000 ft with descent rate. The soft region begins at about 1.3 dots low; the hard region is below 300 ft and at least about two dots low. Both become less sensitive very near the ground, and no Mode 5 alert occurs below 50 ft.

Line 188:		Line 206:
	'''Rise extension — Mode 7 windshear.''' The existing windshear caution/warning logic is implemented, using wind-speed change per elapsed second and vertical wind in atmospheric flight up to 1,500 ft AGL. It is beyond the supplied six-mode MK VI/VIII guide. Its retained coefficients have not been established as a Honeywell or Vieneo aircraft escape-performance model. The old “not currently implemented” label was inaccurate.		'''Rise extension — Mode 7 windshear.''' The existing windshear caution/warning logic is implemented, using wind-speed change per elapsed second and vertical wind in atmospheric flight up to 1,500 ft AGL. It is beyond the supplied six-mode MK VI/VIII guide. Its retained coefficients have not been established as a Honeywell or Vieneo aircraft escape-performance model. The old “not currently implemented” label was inaccurate.
	</div>		</div>

			[[File:GPWS-mode7-Rise-2026.png\|thumb\|center\|1000px\|Mode 7 retained Rise windshear model. Purple identifies a Rise extension, not a manufacturer or Vieneo escape-performance specification.]]

	== Audio behavior and self-test ==		== Audio behavior and self-test ==

codex: Update GPWS for October 2026 implementation; distinguish Rise adaptations in purple, add bank profiles/spaceflight chart, terrain/obstacle display, controls and audio.

2026-10-14T14:47:41Z

Update GPWS for October 2026 implementation; distinguish Rise adaptations in purple, add bank profiles/spaceflight chart, terrain/obstacle display, controls and audio.

Show changes

reskin at 23:16, 22 November 2023

2023-11-22T23:16:39Z

← Older revision		Revision as of 23:16, 22 November 2023
Line 49:		Line 49:
	==Mode 5 - Below Glideslope Deviation Alert==		==Mode 5 - Below Glideslope Deviation Alert==
	[[Image:gpwsmode5.jpg\|left\|Mode 5 Envelope]]		[[Image:gpwsmode5.jpg\|left\|Mode 5 Envelope]]
	This mode alerts you of a descent of more than 1.3 dots below an ILS glideslope. The envelope has two areas of alerting, soft and loud.		This mode alerts you of a descent of more than 1.3 dots below an [[ILS]] glideslope. The envelope has two areas of alerting, soft and loud.
	In both areas is a repeated aural warning of "glideslope". The voice message amplitude is increased when entering the loud area In both areas, the aural warning repetition rate is increased as glideslope deviation increases and radio altitude decreases.		In both areas is a repeated aural warning of "glideslope". The voice message amplitude is increased when entering the loud area In both areas, the aural warning repetition rate is increased as glideslope deviation increases and radio altitude decreases.
	The mode is armed when the [[autoflyte]] vertical mode "G/S" is captured.		The mode is armed when the [[autoflyte]] vertical mode "G/S" is captured.

reskin at 13:49, 21 August 2019

2019-08-21T13:49:51Z

← Older revision		Revision as of 13:49, 21 August 2019
Line 27:		Line 27:

	==Mode 4 - Unsafe Terrain Clearance==		==Mode 4 - Unsafe Terrain Clearance==
			===Mode 4a - Clean Configuration===
	[[Image:gpwsmode4a.jpg\|left\|Mode 4a Envelope]]		[[Image:gpwsmode4a.jpg\|left\|Mode 4a Envelope]]
	~~===Mode 4a - Clean Configuration===~~
	This is the terrain clearance mode with the gear retracted, is armed after take off upon climbing through 215 [[meter\|meters]] [[AGL]]. When this envelope is penetrated at less than a given [[IAS]] the aural alert "struts" is sounded. When the envelope is penetrated at more than a given [[IAS]] the aural alert "too low, terrain" is sounded and the upper boundary of the envelope is increased to 305 [[meter\|meters]] [[AGL]]. The message is repeated until the flight condition has been corrected.		This is the terrain clearance mode with the gear retracted, is armed after take off upon climbing through 215 [[meter\|meters]] [[AGL]]. When this envelope is penetrated at less than a given [[IAS]] the aural alert "struts" is sounded. When the envelope is penetrated at more than a given [[IAS]] the aural alert "too low, terrain" is sounded and the upper boundary of the envelope is increased to 305 [[meter\|meters]] [[AGL]]. The message is repeated until the flight condition has been corrected.
	<br><br><br><br><br><br>		<br><br><br><br><br><br>

			===Mode 4b - Landing Configuration===
	[[Image:gpwsmode4b.jpg\|left\|Mode 4b Envelope]]		[[Image:gpwsmode4b.jpg\|left\|Mode 4b Envelope]]
	~~===Mode 4b - Landing Configuration===~~
	This is not currently implemented		This is not currently implemented
	This mode provides an alert when the gear is down and the flaps are not in landing position. If the envelope is penetrated at less than a given [[IAS]] with the flaps not in the landing position, the aural alert "too low, flaps" is sounded. When the envelope is penetrated at more than a given [[IAS]], the aural alert of "too low, terrain" is sounded and the upper boundary is increased to 305 [[meter\|meters]] [[AGL]]. The voice messages continue to occur until the flight condition has been corrected.		This mode provides an alert when the gear is down and the flaps are not in landing position. If the envelope is penetrated at less than a given [[IAS]] with the flaps not in the landing position, the aural alert "too low, flaps" is sounded. When the envelope is penetrated at more than a given [[IAS]], the aural alert of "too low, terrain" is sounded and the upper boundary is increased to 305 [[meter\|meters]] [[AGL]]. The voice messages continue to occur until the flight condition has been corrected.
Line 39:		Line 39:
	<br><br><br><br>		<br><br><br><br>

			===Mode 4c - Landing Configuration===
	[[Image:mode4c.png\|left\|240px\|Mode 4c Envelope]]		[[Image:mode4c.png\|left\|240px\|Mode 4c Envelope]]

	~~===Mode 4c - Landing Configuration===~~
	This is not currently implemented		This is not currently implemented
	Mode 4C is based on an EGPWS computed Minimum Terrain Clearance (MTC) floor that increases with Radio Altitude. It is active after takeoff when the gear or flaps are not in the landing configuration. It is also active during a low altitude go-around if the aircraft has descended below 245 feet AGL (or 150 feet depending on aircraft type). At takeoff the Minimum Terrain Clearance (MTC) is zero feet. As the aircraft ascends the MTC is increased to 75% of the aircraft’s Radio Altitude (averaged over the previous 15 seconds).		Mode 4C is based on an EGPWS computed Minimum Terrain Clearance (MTC) floor that increases with Radio Altitude. It is active after takeoff when the gear or flaps are not in the landing configuration. It is also active during a low altitude go-around if the aircraft has descended below 245 feet AGL (or 150 feet depending on aircraft type). At takeoff the Minimum Terrain Clearance (MTC) is zero feet. As the aircraft ascends the MTC is increased to 75% of the aircraft’s Radio Altitude (averaged over the previous 15 seconds).
Line 129:		Line 128:
	c. Not currently implemented		c. Not currently implemented
	\|}		\|}



	===Excessive Bank Angle For Altitude===		===Excessive Bank Angle For Altitude===
	For more than 30° of bank left or right you will receive a "BANK ANGLE" callout.		For more than 30° of bank left or right you will receive a "BANK ANGLE" callout.

			==Mode 7 - Windshear ==
	[[Image:winshear.png\|left\|240px\|Windshear Envelope]]		[[Image:winshear.png\|left\|240px\|Windshear Envelope]]

	~~==Mode 7 - Windshear ==~~
	Not currently implemented		Not currently implemented

	[[Category:Avionics]]		[[Category:Avionics]]

reskin: /* Excessive Bank Angle For Altitude */

2019-08-21T13:48:26Z

Excessive Bank Angle For Altitude

← Older revision		Revision as of 13:48, 21 August 2019
Line 133:		Line 133:

	===Excessive Bank Angle For Altitude===		===Excessive Bank Angle For Altitude===
			For more than 30° of bank left or right you will receive a "BANK ANGLE" callout.

			[[Image:winshear.png\|left\|240px\|Windshear Envelope]]

	==Mode 7 - Windshear ==		==Mode 7 - Windshear ==