Physical Transformation AtlasPTA
Claim · claim:flow-drives-mhd

Bulk fluid flow —drives→ Magnetohydrodynamic generation

The atlas records this claim as established: a bulk fluid flow drives magnetohydrodynamic generation under the conditions below.

establishedK7 · engineering prototypeledger kinetic → electrical · loss to thermalno record-level review date

Exploreconditions · evidence · matrix context · uses · cite

3cited sources5enumerated routes using it1routes with composition evidence1recorded pathways

Conditions

  • an electrically conducting fluid — seeded combustion plasma or liquid metal — crossing a strong magnetic field between electrodes
regime: bulk flow required · magnetic field required

Evidence · 3

  1. [1]
    R. J. Rosa. Physical principles of magnetohydrodynamic power generation (1961)
    Physics of Fluids 4, 182–194 · doi:10.1063/1.1724426 · crossref ✓ 2026-09-19 · record
  2. [2]
    L. D. Landau, E. M. Lifshitz, L. P. Pitaevskii. Electrodynamics of Continuous Media (Course of Theoretical Physics, Vol. 8, 2nd ed.) (1984)
    Pergamon · book, no DOI · record
  3. [3]
    NASA Lewis Research Center, Electromagnetic Propulsion Division. Lewis Tech Preview: Research Nonequilibrium MHD Power Generator Facility
    NASA Lewis Research Center tech preview N-422 67/11-39 (one page; the date is not printed beyond that document code) · www1.grc.nasa.gov/wp-content/uploads/MHD-Power-Generator-Facility-Tech-Preview.pdf · record

Matrix cells this relation feeds

D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.

Uses of this claim

recorded pathways · 1
other enumerated routes · 4

Cite this claim

Physical Transformation Atlas (2026). claim claim:flow-drives-mhd: Bulk fluid flow —drives→ Magnetohydrodynamic generation. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/claim/flow-drives-mhd

Ids and matrix addresses are stable across revisions; the revision hash identifies the exact canonical files the record was compiled from and is meta.data_hash in every /api export. Reuse terms: see the license field in any export.