# How to read a plane's descent rate: an ADS-B vertical-speed guide

Riley Quinn · October 12, 2026

> Learn how to read a plane's descent rate using ADS-B vertical-speed data, with FlyDubai flight FZ1073 as a real example of recovery margins in practice.

This guide explains what a plane's descent rate means, using the recorded vertical-speed data from FlyDubai flight FZ1073 to show what recovery margins look like in practice.

 It also gives you a verify-before-you-commit checklist: confirm the live, complete option, and compare like-for-like totals and terms before deciding.

## How It Works

 Reading a descent rate starts with knowing what the airplane actually transmitted. The AP News account of the FlyDubai FZ1073 ordeal describes a multi-hour sequence of steep descents and alternating distress codes, and i24NEWS reports that pilot Smit Machchhar underwent surgery after a cockpit stabbing. Those are narrative accounts. The vertical-speed trace on a public tracker is a separate artifact, built from broadcast data rather than from the cockpit, and the mechanism behind it determines whether any published rate means what it appears to mean.

 The mechanism: airliners continuously broadcast ADS-B Out messages carrying position, altitude, and velocity, each tagged with a timestamp. Vertical rate is not measured directly by the tracker; it is calculated as the change in an altitude field between two successive messages, divided by the time between them. Two altitude fields compete for that job. Barometric altitude comes from the aircraft's static-pressure system, referenced to a standard pressure setting, so it shifts with atmospheric conditions. Geometric altitude comes from satellite navigation and reflects height above a defined reference surface. Most consumer trackers derive vertical rate from the barometric field, so the number you see is a slope between two samples, and it inherits every gap and lag in the feed.

 Four terms do most of the work. Vertical speed, or rate of climb or descent, is that derived slope, expressed in feet per minute or meters per second. Recovery margin is your own arithmetic: altitude remaining above a chosen floor, divided by the current descent rate, yields the time to that floor; recompute it rather than trusting a summary. Sampling interval is the spacing between messages; a coarse interval smooths the slope and hides short, sharp excursions. Coverage gap is a stretch with no messages received, and a slope computed across one is an artifact, not a measurement. The distress codes the AP account describes belong to another category: transponder codes are discrete states a crew selects, so a code change is an event to timestamp, not a trend to average.

 On your next flight, four checks come before any conclusion. Confirm the feed's update interval and whether it holds steady. Identify which altitude field the displayed vertical rate is derived from. Reject any rate computed across a coverage gap. Then compare the barometric and geometric altitude series side by side: when they diverge, the derived rate is describing the atmosphere as much as the airplane.

 Verify-before-you-commit works here the way it does on any booking: confirm the live, complete data set first, then compare like for like — same altitude field, same interval, same window. A steep-looking descent drawn from an incomplete trace is not evidence of a thin recovery margin.

![How It Works — How to read a plane's descent](https://screenshots.mightytravels.com/article-images-ai/how-to-read-a-plane-s-descent-rate-an-ad-ai-9b574b7a.jpg)

## Key Factors to Consider

 When you're deciding whether a recorded descent profile leaves enough recovery margin, three criteria should drive your call before you commit to any interpretation. First: data completeness — confirm the ADS-B feed captured the full vertical profile, not a gap-riddled trace, because a receiver dropout mid-descent can make a smooth descent look like a dive. Second: source consistency — cross-check the vertical speed against a second tracker or the carrier's own statements, the way AP News and i24NEWS each reported distinct pieces of the FlyDubai ordeal before the full picture emerged. Third: like-for-like framing — compare the recorded rate against the same phase of flight on a normal sector, not against a cruise segment or a climb, or you're measuring apples against altimeters.

 The numbers that matter here are the ones you can verify yourself, not the ones you invent. Pull the raw vertical-rate field from the tracker, note the sampling interval, and check whether the reported figure is an instantaneous reading or an average over the interval — the two can differ materially on a steep, dynamic descent. Then confirm the units: feet per minute versus meters per second is the single most common misread in amateur ADS-B analysis, and no interpretation survives a unit error. If the feed doesn't expose the sampling method, treat the figure as indicative only and say so.

| Check | What to verify | If it fails |
| --- | --- | --- |
| Completeness | No gaps across the descent segment | Don't commit to a rate interpretation |
| Units | ft/min vs m/s confirmed in the feed | Recompute before drawing conclusions |
| Averaging | Instantaneous vs interval-average labeled | Flag the figure as indicative only |
| Cross-source | Second tracker or operator statement agrees | Report the discrepancy, not a verdict |

 Margin is the criterion most readers skip. A recorded descent rate tells you what happened, not what headroom existed — and the AP News account of the multi-hour sequence of steep descents and alternating distress codes shows why: the same airframe can cycle through very different vertical profiles in one event, and any single reading is a snapshot, not a capacity statement. Before you commit to a claim about recovery margins, verify you have the complete option set: every descent segment in the trace, each with its own rate, duration, and altitude band.

 Finally, apply the same verify-before-you-commit discipline you'd use on any booking decision. Compare like-for-like totals and terms: same time window, same data source, same phase of flight, same units. If a source gives you a rate without a timestamp, a duration without an altitude, or an altitude without a rate, you don't have a comparable figure — you have a fragment. Commit only when the full record is on the table, and label every gap as a gap rather than smoothing over it.

![Key Factors to Consider — How to read a plane's descent](https://screenshots.mightytravels.com/article-images-pixabay/how-to-read-a-plane-s-descent-rate-an-ad-f82ef9b0.jpg)

## Common Mistakes

 The first common mistake is treating a single steep-descent reading as proof of a near-miss. The AP News account of the FlyDubai FZ1073 ordeal describes a multi-hour sequence of steep descents and alternating distress codes, and i24NEWS reports that pilot Smit Machchhar underwent surgery after a cockpit stabbing. If you pull one ADS-B vertical-speed sample from that sequence and compare it against a normal descent, you are comparing a fragment against a whole. The fix is mechanical: before you judge recovery margin, confirm the feed captured the complete vertical profile — every sample from cruise through the lowest recorded altitude back to level flight. A gap in the trace means you cannot compute a total, and an incomplete total is not a margin. If the full profile is not available, say so and stop; do not fill the gap with an assumed rate.

 The second pitfall is comparing mismatched units and then drawing a conclusion from the mismatch. Vertical speed is transmitted in feet per minute, while altitude is in feet and elapsed time is in minutes or seconds. Dividing a descent rate by an altitude, or multiplying a rate by a time window you guessed rather than measured, produces a number that looks precise and means nothing. Work the arithmetic only in matched units: rate (feet per minute) times duration (minutes) equals altitude change (feet). Recompute every conversion digit by digit before you write it down. If your source gives you a rate but not the duration over which it held, you have one term of a two-term equation — report the missing term, not a fabricated result.

 A third error is letting a dramatic detail stand in for the data. The stabbing and the alternating distress codes are real and serious, but neither one tells you the descent rate, the duration, or the altitude recovered. Keep the narrative and the telemetry in separate columns, and let only the telemetry column drive your margin estimate.

| Check | What to verify | If it fails |
| --- | --- | --- |
| Completeness | Full trace: cruise, descent, recovery | No margin claim |
| Units | Feet per minute vs. feet vs. minutes | Recompute from scratch |
| Like-for-like | Same phase, same duration | Do not compare |

 Run these three checks in order before you commit to any interpretation of a recorded descent rate. Completeness first, units second, like-for-like third. If any check fails, the honest output is a question, not a verdict — and on your next flight, that habit is what keeps a dramatic headline from becoming a false conclusion.

![Common Mistakes — How to read a plane's descent](https://screenshots.mightytravels.com/article-images-pixabay/how-to-read-a-plane-s-descent-rate-an-ad-cbc8eec0.jpg)

## Insider Tactics

 The non-obvious strategy is to watch the vertical-speed trend across several consecutive ADS-B updates, not the single largest number on the screen. In the FlyDubai FZ1073 case, AP News describes a multi-hour ordeal with steep descents and alternating distress codes — meaning the recorded profile moved up and down repeatedly. A one-off steep reading tells you far less than a sustained pattern: pull up the flight's track, note the vertical speed at each timestamp, and ask whether the same direction of travel holds for three or more consecutive reports. If it does, you're looking at a real maneuver; if it flips between climb and descent within a minute or two, treat the spike as noise or a transient event and withhold judgment until the full sequence is visible.

 The timing tip most people miss: check the feed's update cadence before you interpret anything. ADS-B receivers on the ground don't transmit at perfectly even intervals, and gaps in coverage can make two distant data points look like a single rapid descent. Before committing to a conclusion, confirm the timestamps between the points you're comparing — if the interval between updates is unusually long, the computed rate over that gap is unreliable, and you should anchor your reading to the densely spaced portion of the track instead. Note that the news reports cited here (AP News on the cockpit fight and steep descents, i24NEWS on the pilot's surgery) describe the event but do not publish the telemetry itself; whether the FZ1073 record is complete is something you must verify on the tracker, not assume from the reporting.

 A second tactic: cross-check two independent aggregators showing the same flight before you trust any single vertical-speed figure. If both feeds show the same descent trend at overlapping timestamps, your confidence in the reading rises sharply; if they disagree, the receiver coverage — not the aircraft — is the likely culprit, and you should wait for the track to fill in.

 Timing matters on the back end, too. If you're reviewing a flight that just made an unusual maneuver, give the feed time to finalize before you screenshot or share. Early tracks are the most prone to gaps and corrections, and a track pulled minutes after the event can look materially different from the same track an hour later. The verify-before-you-commit rule applies to the data itself: confirm the live, complete record before you treat any single reading as the story.

 Finally, apply the like-for-like rule to your own comparisons. When you evaluate a descent profile, compare segments of similar length and similar update density — a rate computed over a dense stretch of data versus one computed over a sparse gap is not a fair comparison, and treating them as equivalent is how a routine descent gets mistaken for an emergency. Match the segments first, then judge the margin.

![Insider Tactics — How to read a plane's descent](https://screenshots.mightytravels.com/article-images-pixabay/how-to-read-a-plane-s-descent-rate-an-ad-db44e402.jpg)

## Comparison

 When you're deciding how to judge a recorded descent profile like the one reported on FlyDubai FZ1073 — where AP News describes a multi-hour ordeal with steep descents and alternating distress codes — you have three practical ways to pull the vertical-speed picture, and they are not interchangeable. The comparison below is the side-by-side you should run before committing to any interpretation, and it has a clear winner for a traveler verifying data on their own flight.

| Option | What you get | When it wins | When it loses |
| --- | --- | --- | --- |
| Aggregated tracker site (single summary view) | One averaged vertical-rate figure per flight, pre-smoothed | Quick sanity check on a routine flight | Hides gaps and spikes; a smoothed average can erase the very steep segments you're checking for |
| Raw ADS-B message feed (per-report vertical rate) | Every transmitted vertical-speed sample, timestamped, including gaps | Verifying recovery margin on an unusual profile — the verify-before-you-commit case | Slower to read; requires checking sample continuity yourself |
| Official investigation or carrier statement | Authoritative account of what happened in the cockpit | Confirming cause after the fact — as i24NEWS did in reporting that the pilot underwent surgery after averting disaster | Not available in real time; useless as a live pre-commitment check |

 The winner for your next flight is the raw feed, and here's the like-for-like logic: the aggregated view and the raw feed draw from the same ADS-B transmissions, so they're comparable on data source — but only the raw feed lets you confirm completeness, which is the precondition for trusting any descent-rate reading. The official statement is a different category entirely: it explains, it doesn't verify. Comparing a summary site against an investigation report is not a like-for-like comparison; comparing raw samples against a summary of those same samples is.

 Run the comparison with this rule: if the raw feed and the aggregated summary disagree on the presence of a steep segment, the raw feed wins — an average cannot create a steep descent that wasn't transmitted, but it can flatten one that was. If the raw feed shows gaps where the summary shows a smooth line, treat the summary as unverified and withhold commitment until the gap is explained.

 Each option also wins in a different situation. The aggregated tracker wins when you only need to confirm a flight is behaving normally and you have seconds, not minutes. The raw feed wins whenever the profile looks unusual — that's the moment the verify-before-you-commit rule applies with full force. The official account wins last, as the final word: AP News's reporting on the FZ1073 sequence is the kind of source you reconcile against after the fact, not before. Sequence your checks in that order — summary, raw feed, official statement — and you'll never commit on an incomplete option.

Also worth reading
 [FlyDubai Tel Aviv route cut: 2026](https://www.mightytravels.com/2026/10/flydubai-tel-aviv-route-cut-2026-israel-award-seats-vs-cash-fares-on-star-alliance/)
·
 [How global conflicts are impacting](https://www.mightytravels.com/2026/03/how-global-conflicts-are-impacting-your-flight-costs-and-what-it-means-for-your-next-trip/)
·
 [How to claim your free flight](https://www.mightytravels.com/2026/06/how-to-claim-your-free-flight-to-hong-kong-and-save-on-your-next-trip/)

## What to do next

| Step | Action | Why it matters |
| --- | --- | --- |
| 1 | Open the live ADS-B vertical-speed trace for FlyDubai flight FZ1073 and confirm it is the complete, current record — not a cached or partial snapshot. | The descent-rate reading only means something if you are looking at the full, live option set rather than a fragment of it. |
| 2 | On that trace, isolate the steep-descent segments and read each vertical-speed value on its own terms: note the timestamp, the sampling interval, and whether the rate holds across consecutive reports. The alternating distress codes reported during the 4-hour ordeal are events to timestamp separately — per the article's own rule, keep the narrative and the telemetry in separate columns and let only the telemetry drive any margin estimate. | Pairing each descent rate with the distress code active at that moment is what turns a raw number into a recovery-margin signal. |
| 3 | Cross-check the trace against a second independent tracker showing the same flight at overlapping timestamps. The AP News and i24NEWS accounts describe what happened in the cockpit; they are narrative sources to reconcile after the fact, not telemetry to match figures against, so treat any disagreement between them and the feed as a prompt to check receiver coverage rather than a verdict. | Matching totals against totals and terms against terms keeps the data comparison on the same basis as the reporting. |
| 4 | Before drawing any conclusion about recovery margins, verify the live, complete option — the full FZ1073 record — rather than committing on the basis of one descent segment. | A single steep descent, read in isolation, cannot tell you what margin the crew actually had. |
| 5 | Compare like-for-like within the telemetry: match descent-rate figures against descent-rate figures, computed over the same altitude field, the same sampling interval, and the same phase of flight. Do not mix a telemetry figure with a narrative detail from the news accounts — the two measure different things and cannot be placed on the same basis. | Comparisons only reflect reality when both sides are measured the same way. |
| 6 | Only after the full FZ1073 record is confirmed live and complete, commit to your reading of what the descent rate means for recovery margins. | The decision rule is the same one the data demands: verify the live, complete option before committing. |

## Frequently Asked Questions

 **Is the public tracker's vertical-speed trace the same evidence as the cockpit narrative of the FlyDubai flight?**

 No: the AP News account describes a multi-hour sequence of steep descents and alternating distress codes, while the tracker trace is a separate artifact built from broadcast data rather than from the cockpit.

 **Does the tracker measure vertical rate directly from the airplane?**

 No: vertical rate is calculated as the change in an altitude field between two successive messages divided by the time between them.

 **What do airliners continuously broadcast in ADS-B Out messages?**

 Position, altitude, and velocity, each tagged with a timestamp.

 **Which altitude field comes from the aircraft's static-pressure system?**

 Barometric altitude comes from the aircraft's static-pressure system and is referenced to a standard pressure setting.

 **What should the verify-before-you-commit checklist confirm before deciding?**

 Confirm the live, complete option, and compare like-for-like totals and terms before deciding.

 **What did i24NEWS report about pilot Smit Machchhar after the cockpit stabbing?**

 i24NEWS reports that pilot Smit Machchhar underwent surgery after a cockpit stabbing.

## Quick answers

| What does a plane's descent rate mean in the context of this guide? | This guide explains what a plane's descent rate means, using the recorded vertical-speed data from FlyDubai flight FZ1073 to show what recovery margins look like in practice. |
| --- | --- |
| What checklist does the guide provide before deciding? | It also gives you a verify-before-you-commit checklist: confirm the live, complete option, and compare like-for-like totals and terms before deciding. |
| What does reading a descent rate start with? | Reading a descent rate starts with knowing what the airplane actually transmitted. |
| How is vertical rate calculated by the tracker? | Vertical rate is not measured directly by the tracker; it is calculated as the change in an altitude field between two successive messages, divided by the time between them. |
| Where does barometric altitude come from? | Barometric altitude comes from the aircraft's static-pressure system, referenced to a standard pressure setting, so it shifts with atmospheric condi |

Canonical: https://www.mightytravels.com/2026/10/how-to-read-a-planes-descent-rate-an-ads-b-vertical-speed-guide/
Markdown: https://www.mightytravels.com/2026/10/how-to-read-a-planes-descent-rate-an-ads-b-vertical-speed-guide/index.md