Skip to content

Cumulonimbus incus

Identify the mature anvil-bearing cumulonimbus species whose glaciated upper cloud spreads beneath a stable layer after vigorous convection reaches its equilibrium-level region, while treating associated severe weather as possible consequences rather than defining features.

Version
v2 · 2026-08-30 · History
Domain-specific #
1605
Origin domain
atmospheric science
Subdomain
cloud classification and deep convection

Core Idea

Cumulonimbus incus is the incus supplementary feature of a mature cumulonimbus capillatus cloud: its glaciated, fibrous upper part has spread laterally into the characteristic anvil form near a stable upper boundary.[1][1] deep moist convection carries condensate upward until buoyancy weakens near the equilibrium-level or tropopause region; ice-dominated outflow then spreads laterally, and environmental winds can shear the spreading canopy away from the active updraft.

Its autonomous residual is the formal cloud-morphology identity joining mature cumulonimbus, a glaciated capillatus summit, and laterally spread incus form; severe-weather association, storm intensity, and visual resemblance to an anvil are not sufficient alone. The identity fails when the parent cloud is not cumulonimbus, the upper feature is a smooth nonfibrous calvus dome, a cap-shaped plume was created by an impulsive source rather than cloud convection, the anvil is detached and no longer attributable, or hazard occurrence is substituted for morphological recognition.

Recognition requires an analyst to establish cumulonimbus identity and life-cycle context, identify the fibrous or striated glaciated top and anvil spreading, separate the active tower from detached cirrus, and report viewing geometry or remote-sensing uncertainty before assigning the incus feature. Once established, it supports cloud reporting, storm-stage interpretation, satellite and field-observation annotation, comparison of convective organization, and qualified recognition of environments in which lightning, hail, heavy precipitation, downbursts, or tornado-producing storms may occur without turning those uses into the definition.

Structural Signature

  • Carrier: a vertically developed cumulonimbus cloud observed within a specified atmospheric sounding, storm life-cycle stage, and cloud-classification convention
  • Inputs or antecedent state: cloud silhouette and texture, evidence of fibrous or striated upper-cloud glaciation, anvil outflow, vertical development, environmental stability and wind profile, observation time, and any radar or satellite context
  • Constitutive operation: deep moist convection carries condensate upward until buoyancy weakens near the equilibrium-level or tropopause region; ice-dominated outflow then spreads laterally, and environmental winds can shear the spreading canopy away from the active updraft
  • Invariant: the object is a cumulonimbus cloud with a capillatus, ice-fibrous upper region that spreads into a distinct anvil rather than merely any tall cloud, any flattened cloud top, or any thunderstorm hazard
  • Recognition test: establish cumulonimbus identity and life-cycle context, identify the fibrous or striated glaciated top and anvil spreading, separate the active tower from detached cirrus, and report viewing geometry or remote-sensing uncertainty before assigning the incus feature
  • Output or consequence: cloud reporting, storm-stage interpretation, satellite and field-observation annotation, comparison of convective organization, and qualified recognition of environments in which lightning, hail, heavy precipitation, downbursts, or tornado-producing storms may occur
  • Failure boundary: the parent cloud is not cumulonimbus, the upper feature is a smooth nonfibrous calvus dome, a cap-shaped plume was created by an impulsive source rather than cloud convection, the anvil is detached and no longer attributable, or hazard occurrence is substituted for morphological recognition

What It Is Not

  • It is not the whole field of atmospheric science; many objects in that field do not satisfy its constitutive rule.
  • It is not its canonical example. A vigorous convective tower matures until its upper ice cloud spreads horizontally beneath the tropopause, producing a broad fibrous canopy attached to the cumulonimbus tower. That is an instance, not a definition.
  • It is not Storm. Storm is the broad atmospheric-disturbance category and Mushroom Cloud is a source-driven buoyant-plume morphology; neither fixes the WMO cumulonimbus species and incus supplementary feature.
  • It is not an unrestricted metaphor. a sheared or partly obscured anvil can remain incus when the glaciated spread and cumulonimbus continuity are demonstrable, while a visual cap-and-stem resemblance without convective-cloud lineage is insufficient

Scope of Application

Cumulonimbus incus applies when the analyst can specify a vertically developed cumulonimbus cloud observed within a specified atmospheric sounding, storm life-cycle stage, and cloud-classification convention and establish that the object is a cumulonimbus cloud with a capillatus, ice-fibrous upper region that spreads into a distinct anvil rather than merely any tall cloud, any flattened cloud top, or any thunderstorm hazard. The entry classifies cloud morphology and its physical interpretation; it does not diagnose a particular storm hazard, replace official forecasts, or turn an anvil sighting into operational safety advice.[2]

  • Recognition. establish cumulonimbus identity and life-cycle context, identify the fibrous or striated glaciated top and anvil spreading, separate the active tower from detached cirrus, and report viewing geometry or remote-sensing uncertainty before assigning the incus feature
  • Comparison. Compare legitimate instances through parent cloud species, glaciation texture, anvil attachment, vertical maturity, equilibrium-level relation, environmental wind shear, viewing geometry, observation platform, life-cycle stage, and hazard evidence.
  • Boundary. a sheared or partly obscured anvil can remain incus when the glaciated spread and cumulonimbus continuity are demonstrable, while a visual cap-and-stem resemblance without convective-cloud lineage is insufficient
  • Use. Preserve every assumption when using the identity for cloud reporting, storm-stage interpretation, satellite and field-observation annotation, comparison of convective organization, and qualified recognition of environments in which lightning, hail, heavy precipitation, downbursts, or tornado-producing storms may occur.

Clarity

A clear claim names the carrier, governing rule, assumptions, and recognition test. This matters because thunderhead and anvil cloud are informal surfaces that may be used loosely, whereas incus is a typed feature whose recognition depends on the parent species, ice texture, and spreading form. The disciplined statement is that the object counts as Cumulonimbus incus exactly when the object is a cumulonimbus cloud with a capillatus, ice-fibrous upper region that spreads into a distinct anvil rather than merely any tall cloud, any flattened cloud top, or any thunderstorm hazard

Identity and measurement remain separate. Visual recognition depends on illumination, distance, obstruction, temporal sampling, and observer training; satellite brightness or radar echo alone is an imperfect proxy for the formal cloud feature and for surface consequences. Approximation or noisy evidence may weaken a classification without changing its definition.

Manages Complexity

The abstraction compresses symmetric and strongly sheared anvils, isolated and multicellular storms, tropical and midlatitude convection, visual, satellite, and radar-assisted observations, and attached versus dissipating canopy stages into a stable carrier, rule, invariant, and failure boundary. It makes comparison tractable while retaining the variables that control validity.

Compression can hide assumptions. A responsible use therefore declares parent cloud species, glaciation texture, anvil attachment, vertical maturity, equilibrium-level relation, environmental wind shear, viewing geometry, observation platform, life-cycle stage, and hazard evidence and returns to the full diagnostic whenever a convention or boundary case changes.

Abstract Reasoning

  1. Type the carrier. Establish a vertically developed cumulonimbus cloud observed within a specified atmospheric sounding, storm life-cycle stage, and cloud-classification convention and reject examples from a different problem.
  2. Lock the rule. Express that the object is a cumulonimbus cloud with a capillatus, ice-fibrous upper region that spreads into a distinct anvil rather than merely any tall cloud, any flattened cloud top, or any thunderstorm hazard independently of one notation or implementation.
  3. Derive carefully. Infer cloud reporting, storm-stage interpretation, satellite and field-observation annotation, comparison of convective organization, and qualified recognition of environments in which lightning, hail, heavy precipitation, downbursts, or tornado-producing storms may occur only under the stated assumptions.
  4. Stress-test. Contrast the legitimate boundary case—a sheared or partly obscured anvil can remain incus when the glaciated spread and cumulonimbus continuity are demonstrable, while a visual cap-and-stem resemblance without convective-cloud lineage is insufficient—with this counterexample: a nuclear or volcanic mushroom cloud may display a broad cap above a stem but is not cumulonimbus incus because its source, thermodynamic history, hydrometeor structure, and cloud-classification identity differ.

Knowledge Transfer

Transfer within atmospheric science is strong when new cases preserve the same carrier, mechanism, and diagnostic. The move from A vigorous convective tower matures until its upper ice cloud spreads horizontally beneath the tropopause, producing a broad fibrous canopy attached to the cumulonimbus tower. to A geostationary satellite sequence shows overshooting convective texture near an active core and a downwind ice canopy expanding over several hours. demonstrates that continuity.[3]

Outside the domain, only the skeleton—a gradient-driven rising flow reaches a limiting layer and redirects laterally, leaving a morphology that records both the source circulation and the boundary—travels automatically. The terms cumulonimbus, capillatus, incus, anvil, glaciation, equilibrium level, tropopause, overshooting top, updraft, outflow, and wind shear retain domain-specific meanings, so every role and inference must be revalidated.

Examples

Canonical

A vigorous convective tower matures until its upper ice cloud spreads horizontally beneath the tropopause, producing a broad fibrous canopy attached to the cumulonimbus tower. The vertical tower supplies the cumulonimbus carrier, the ice-textured spreading top supplies capillatus and incus morphology, and the attachment and observation sequence distinguish the anvil from unrelated cirrus.[2] It is canonical because the carrier, rule, invariant, and consequence are all inspectable.[1]

Mapped back: a vertically developed cumulonimbus cloud observed within a specified atmospheric sounding, storm life-cycle stage, and cloud-classification convention → deep moist convection carries condensate upward until buoyancy weakens near the equilibrium-level or tropopause region; ice-dominated outflow then spreads laterally, and environmental winds can shear the spreading canopy away from the active updraft → the object is a cumulonimbus cloud with a capillatus, ice-fibrous upper region that spreads into a distinct anvil rather than merely any tall cloud, any flattened cloud top, or any thunderstorm hazard → cloud reporting, storm-stage interpretation, satellite and field-observation annotation, comparison of convective organization, and qualified recognition of environments in which lightning, hail, heavy precipitation, downbursts, or tornado-producing storms may occur

Applied / In Practice

A geostationary satellite sequence shows overshooting convective texture near an active core and a downwind ice canopy expanding over several hours. The expanding canopy can support an incus annotation when shape, texture, attachment, and storm evolution agree, but the image alone does not establish surface hail, tornado occurrence, or a particular warning category.[3] It qualifies only after the same diagnostic and failure boundary are checked.[2]

Mapped back: declared instance → recognition test → boundary check → qualified use

Structural Tensions

  • T1: Exact identity vs. practical recognition. The constitutive condition may be exact while evidence is indirect. Diagnostic: Can the reviewer state both the condition and the warrant?
  • T2: Canonical form vs. variants. symmetric and strongly sheared anvils, isolated and multicellular storms, tropical and midlatitude convection, visual, satellite, and radar-assisted observations, and attached versus dissipating canopy stages can preserve or change the identity. Diagnostic: Which named role is invariant across the variants?
  • T3: Compression vs. hidden assumptions. The label is useful only while prerequisites remain visible. Diagnostic: Can each downstream inference be traced to a declared assumption?
  • T4: Autonomy vs. reduction. The candidate uses broader structures but claims the formal cloud-morphology identity joining mature cumulonimbus, a glaciated capillatus summit, and laterally spread incus form; severe-weather association, storm intensity, and visual resemblance to an anvil are not sufficient alone. Diagnostic: Does that residual still support independent recognition after the parent and neighbors are subtracted?

Structural–Framed Character

The entry is structurally mixed but domain-framed. Its portable skeleton is a gradient-driven rising flow reaches a limiting layer and redirects laterally, leaving a morphology that records both the source circulation and the boundary; its identity-bearing terms are cumulonimbus, capillatus, incus, anvil, glaciation, equilibrium level, tropopause, overshooting top, updraft, outflow, and wind shear. Those terms determine admissible objects, evidence, and consequences inside atmospheric science.

Structural Core vs. Domain Accent

The structural core is a carrier governed by deep moist convection carries condensate upward until buoyancy weakens near the equilibrium-level or tropopause region; ice-dominated outflow then spreads laterally, and environmental winds can shear the spreading canopy away from the active updraft and tested by establish cumulonimbus identity and life-cycle context, identify the fibrous or striated glaciated top and anvil spreading, separate the active tower from detached cirrus, and report viewing geometry or remote-sensing uncertainty before assigning the incus feature. The domain accent is constitutive rather than decorative, so an analogy that preserves only the skeleton is not another instance of Cumulonimbus incus.

The proposed strict upward parent is prime:convection. Deep moist convection literally supplies the vertical circulation that builds the parent cumulonimbus and delivers condensate to the upper stable layer; glaciation, formal morphology, and anvil spreading provide the autonomous meteorological residual. The edge is proposal-only and points to a frozen prior-baseline Prime.

The entry does not collapse into the parent because the formal cloud-morphology identity joining mature cumulonimbus, a glaciated capillatus summit, and laterally spread incus form; severe-weather association, storm intensity, and visual resemblance to an anvil are not sufficient alone A thematic neighbor is declined whenever it does not literally subsume that rule.

The prospective workspace queue contains one strict upward edge to prime:convection. No live DAG mutation is authorized.

Relationships to Other Abstractions

Local relationship map for Cumulonimbus incusParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Cumulonimbus incusDOMAINPrime abstraction: Convection — is a kind ofConvectionPRIME

Current abstraction Cumulonimbus incus Domain-specific

Parents (1) — more general patterns this builds on

  • Cumulonimbus incus is a kind of Convection Prime

    The proposed strict upward parent is prime:convection.

Hierarchy paths (3) — routes to 3 parentless roots

Neighborhood in Abstraction Space

Cumulonimbus incus sits in a moderately populated region (60th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Weather, Climate & Atmospheric Dynamics (32 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08

Not to Be Confused With

  • Cumulonimbus calvus. The earlier smooth or cauliflower-topped stage before the upper part acquires the distinctly fibrous, glaciated capillatus appearance.
  • Cumulonimbus capillatus. The species defined by fibrous upper cloud; incus is the particular anvil-form supplementary feature within that mature morphology.
  • Overshooting top. A local dome or plume penetrating above the surrounding anvil, not the laterally spread anvil itself.
  • Shelf cloud. A low horizontal accessory cloud associated with gust-front outflow rather than the high glaciated cumulonimbus summit.
  • Mushroom cloud. An impulsively generated buoyant plume whose superficial stem-and-cap outline does not confer WMO cumulonimbus identity.

References

[1] World Meteorological Organization, International Cloud Atlas: Manual on the Observation of Clouds and Other Meteors, 2017 edition, entries for Cumulonimbus capillatus and the incus supplementary feature. registry ↩a ↩b ↩c

[2] American Meteorological Society, Glossary of Meteorology, entry 'incus,' updated online reference edition. registry ↩a ↩b ↩c

[3] Charles A. Doswell III, 'Severe Convective Storms—An Overview,' Meteorological Monographs 28(50), 1–26 (2001), DOI 10.1175/0065-9401-28.50.1. registry ↩a ↩b