Evidence audit · NASA SUCCESS · April 10, 1996

A contrail formed—and then disappeared too quickly to re-enter

During a NASA research flight, the DC-8 deliberately crossed its own exhaust region after producing contrails at several altitudes. The mission record says the trails were not persistent enough for the aircraft to circle back into them. This “negative” result cleanly separates formation from persistence.

Case verdict

Formation: observedNASA’s mission report explicitly records contrails produced by the DC-8.
Persistence: not observedThe trails were described as too short-lived to re-enter on a circle.
Why it mattersA formation-positive case can still be persistence-negative under the surrounding humidity.

Our conclusion is limited to the mission report: the research aircraft generated visible trails that did not last long enough for the planned re-entry. We do not infer an exact lifetime, humidity value, or formation threshold because the summary does not provide those measurements for each trail.

The documented record

SUCCESS—the SUbsonic aircraft: Contrail & Clouds Effects Special Study—was a NASA field campaign from April 2 through May 15, 1996 across the central and western United States. NASA’s ER-2, DC-8, and T-39 carried remote-sensing and in-situ instruments to study clouds, aerosols, contrails, radiation, and atmospheric chemistry, supported by ground observations at the Department of Energy ARM site.

The April 10 mission was a DC-8 test flight and transit from Ames. NASA’s daily schedule records scattered cirrus near Ames, little or no cirrus across portions of the route, and marine stratus elsewhere. In restricted airspace, the DC-8 produced non-persistent contrails over a range of flight levels. The report states they did not survive long enough for the aircraft to return on a circular path, although the DC-8 made multiple crossings of its own exhaust plume.

Evidence ledger for this audit.
EvidenceClassificationWhat it supportsWhat it does not establish
NASA daily mission scheduleContemporaneous operational summaryAircraft, mission context, intentional plume crossings, and non-persistent outcome.Exact RHi, temperature, lifetime, or microphysical evolution for each segment.
SUCCESS campaign descriptionOfficial campaign metadataResearch purpose, dates, geography, platforms, and instrument categories.Results for this individual trail without the daily record/data.
Established contrail physicsMechanistic frameworkWhy formation can occur before crystals sublimate in ice-subsaturated air.The exact cause of short lifetime without a measured local humidity profile.

Reasoning step by step

  1. The source aircraft is unusually well constrained

    This was not an attempt to match an anonymous line to a public flight icon. The research mission intentionally studied its own plume, so the source relationship is documented at a level rarely available to a ground observer.

  2. Visible formation occurred

    The mission log’s use of “contrails” establishes that at least portions of the exhaust plume formed visible ice cloud. The Schmidt–Appleman formation conditions were therefore met locally, even though we cannot reconstruct the exact threshold from the summary.

  3. Persistence did not follow

    The planned circular re-entry required the trail to remain in place long enough for the DC-8 to return. NASA’s record says it did not. That outcome is consistent with ambient air below ice saturation, which allows new crystals to sublimate after plume dilution.

  4. The negative outcome is scientifically informative

    If a model labels every cold, high-altitude flight as persistent, this case exposes the error. A useful system must predict non-events and rapidly disappearing events, not only visually striking successes.

Alternative explanations and what the record says

“No contrail formed”

Contradicted by the NASA daily report, which explicitly records non-persistent contrails.

“A persistent trail formed but moved before re-entry”

Strong wind could complicate an intercept, but the mission summary characterizes the issue as insufficient persistence rather than displacement. Without the detailed flight/science log we cannot independently time that assessment, so we retain the official classification.

“The result applies to all altitudes and aircraft”

Not supported. The report covers one mission and broad altitude tests. Small vertical changes can cross a humidity boundary; another engine or air mass can have a different outcome.

What this case demands from our map

A Contrail Research reconstruction should keep four outputs distinct:

  • Flight track: the DC-8 path is observed navigation context.
  • Formation plausibility: a temperature/pressure/engine calculation can be positive.
  • Persistence plausibility: an independent humidity-with-respect-to-ice test can be negative.
  • Observed lifetime: the mission’s own visual/instrument record is the validation target.

If the model rendered a durable cloud cell for this event, that would be a false persistence signal even if a brief trail line were correct. This distinction is why map “support” must never be treated as a calibrated probability or a direct observation.

Limitations of this case study

  • The public daily schedule is a concise operational narrative, not the complete instrument dataset.
  • It does not give an exact lifetime, position, temperature, pressure, or RHi for each produced trail.
  • The broad altitude description should not be interpreted as evidence that identical plume physics occurred continuously through the full range.
  • We have not rerun the 1996 event because the necessary synchronized records are not available on this page.
  • Lessons about separating formation and persistence generalize; numerical thresholds from this case do not.

Sources

  1. NASA Airborne Science Program: SUCCESS April 10, 1996 mission daily schedule.
  2. NASA Earthdata: SUCCESS campaign overview.
  3. Schumann, U. (1996). On conditions for contrail formation from aircraft exhausts.

Editorial note: descriptions above paraphrase the linked records. Where the source lacks a number, we do not supply one.