Transport Phenomena (PD 26-366Y): NSF 2026 Open Grant Window for Multiscale Fluid and Energy Transport Research

Transport Phenomena (PD 26-366Y): NSF 2026 Open Grant Window for Multiscale Fluid and Energy Transport Research

The NSF Transport Phenomena program is a broad, high-competition but open-ended 2026 intake route for engineering science that combines fundamental transport physics with societal impact. Unlike a one-off RFA with a single deadline, this program is currently posted as a continuing submission channel with a live call for full proposals, which makes it suitable for teams that need more planning runway than a fixed-cycle solicitation typically provides.

The program was published on 24 April 2026 and is hosted by NSF’s Directorate for Engineering (ENG), specifically the Division of Chemical, Bioengineering, Environmental and Transport Systems (CBET). The page states a single operationally critical routing rule: full proposals are submitted through Research.gov under NSF 24-1 with the ENG/CBET pathway and the program name selected. On the same page, it is also stated that proposals for this program cannot currently be submitted through Grants.gov.

This is a practical fit for projects where the core science is transport-driven but the team can show clear national-priority relevance.

Key details

What Transport Phenomena covers and why this matters

The program text emphasizes foundational research in transport of mass, momentum, energy, and species, with explicit encouragement for work spanning multiple scales. This wording is important because it implies the program is not only for incremental experiments in a narrow subtopic. It rewards work that starts at a physical mechanism and scales toward system behavior.

The page lists priority thematic areas in enough detail to make fit-checking concrete:

• single- and multiphase systems,
• transition to turbulence,
• flow separation,
• drag reduction,
• cavitation,
• reactive flows,
• transport at fluid-fluid and fluid-solid interfaces,
• combustion dynamics including chemical kinetics and turbulence-chemistry interactions,
• wildland fire behavior in WUI contexts,
• and thermal transport, including phase transitions, radiation, and microscale-to-device applications.

It also explicitly links TP outcomes to sectors like AI, manufacturing, biotechnology, microelectronics, energy, nuclear energy, and quantum science and engineering. That breadth is meaningful because it gives teams room to frame technical advances in domain language that NSF reviewers and partners can evaluate beyond one siloed discipline.

In practical terms, this opportunity is often strongest for teams building a clear story in one of two directions:

1. Fundamental insight that can improve transport models, materials behavior, and experimental interpretation.
2. Process-relevant transfer pathways where the same core science informs national priority applications, such as cleaner combustion, efficient thermal management, or safety-critical flows.

A weak proposal is typically one that presents technically interesting transport effects but does not define why they matter to measurable system outcomes.

Who should treat this as a fit versus a mismatch

This is a good opportunity for principal investigators and teams with one of the following profiles:

• University-based groups in fluid mechanics, mechanical engineering, chemical engineering, combustion, thermal systems, or energy systems.
• Research teams with enough depth to connect molecular or mesoscale transport understanding with larger-scale performance indicators.
• Labs proposing cross-pollination between transport theory and systems work (for example, AI-guided modelling of multiphase flows or transport-limited reactor design).
• Collaborations with industry or federal partners where the output can support measurable improvements in operational resilience, efficiency, or diagnostics.

This is likely a weaker fit if:

• The concept does not include a transport-specific mechanism and is mostly materials or software-only without real transport coupling.
• The proposal is framed as near-term product development without a scientific core in transport dynamics.
• The submission team cannot reliably operate within NSF’s Research.gov route and does not have proposal office support to handle PAPPG and compliance constraints.

The page also references a dedicated update about partnership opportunities through NSF ENG Partnerships. That is relevant if you are considering co-development or translational extension with external stakeholders, but the central requirement remains technical and process fit.

Eligibility and submission mechanics that matter most

The program page is short on an expanded eligibility section, so the safest interpretation is to treat this as a standard NSF full-proposal pathway with additional program routing constraints. The following should be treated as operationally non-negotiable:

1. Use Research.gov as the active route per the official statement.
2. Select NSF 24-1, then ENG, then CBET, then the program path.
3. Use the NSF Proposal & Award Policies & Procedures Guide as the governing compliance framework.
4. Do not assume Grants.gov is the right path for this program at this moment.

Because this opportunity does not publish a unique PI profile matrix in the visible summary, teams should verify whether any additional eligibility details are in underlying PAPPG sections or program contact guidance before submission.

When eligibility is not repeated in one place, teams are often penalized not on science quality but on filing mistakes. The fastest way to avoid that is a pre-submission compliance memo that includes:

• lead institution type,
• PI PI/Co-PI responsibilities,
• conflict-of-interest checks,
• data-management expectations,
• budget assumptions,
• and NSF submission-system verification.

Make sure these are finalized before full narrative drafting. In continuous-opportunity programs, teams often lose time because they draft the science section first and later discover routing errors.

Application process and required preparation flow

Because there is no fixed closing date listed and the call is effectively open, preparation quality becomes a function of internal process, not calendar urgency. A strong workflow is:

1) Convert the broad page into a scoped call statement

Define one sentence that maps your project to the official scope language. For example: “This project addresses transport across multiphase boundaries and improves thermal or momentum transport in a system with explicit energy/manufacturing relevance.” Every section should trace back to this statement.

2) Confirm topic alignment to named domains

Before writing, map your abstract to explicit TP topics:

• turbulence-chemistry coupling,
• multiscale interaction across micro and macro transport regimes,
• interface transport,
• thermal transport and phase behavior,
• combustion dynamics,
• wildland interface transport concerns (if relevant).

A proposal that can only claim tangential overlap is at risk under competitive NSF review.

3) Build a transport-specific evidence plan

For this opportunity, evidence quality should combine three layers:

• mechanistic understanding,
• measurement/model coherence,
• and expected impact pathway.

If your proposal includes computational and experimental parts, ensure validation paths are explicit and shared across team members. Reviewers in NSF engineering tracks often check whether a mechanism is scientifically testable, not just compellingly written.

4) Build NSF-style package quality early

Although no fixed award amount is published on this page, your budget still needs to be coherent with the technical plan, staffing, facility usage, and expected outputs. Include:

• a justified cost breakdown,
• realistic timeline,
• deliverables with clear dependencies,
• and milestone structure that supports periodic NSF-style reporting.

5) Route dry-run

Use the same deadline discipline you would for a fixed-cycle program:

• verify system credentials,
• verify division/program routing,
• verify proposal title and program path,
• run a mock submission check with admin staff.

A single routing mistake can remove an otherwise strong proposal from review.

What to include in your proposal narrative

For a broad program like TP, you gain advantage by using a clear structure that repeatedly links mechanism to transport relevance:

Project significance

State why the transport bottleneck is not just interesting scientifically but limiting real system performance.

Methods

Explain whether your work is experimental, computational, or hybrid, and show how methods connect scales. If the study includes AI/ML, justify why the algorithmic layer improves transport understanding, not just model aesthetics.

Transport mechanism and scaling logic

NSF pages emphasize that TP supports cross-scale work. Show explicitly how knowledge at one scale affects macroscale behavior. If this link is missing, the proposal may read as disconnected work.

Impact narrative

Use application sectors as anchors: manufacturing efficiency, energy conversion, clean systems, AI-enabled engineering, nuclear systems, or related high-impact sectors. Keep this section specific and measurable.

Risk and uncertainty

NSF reviewers frequently see transport models overstate certainty. Identify assumptions, model limits, and mitigation steps. This section should align with your measurement plan, not just narrative reassurance.

Common mistakes and what reviewers may interpret as weak

Treating “open anytime” as “low discipline”

An open deadline does not reduce review standards. If anything, this increases importance of internal rigor because you no longer have a single external gate to force a final quality pass.

Vague topic mapping

A common loss point is selecting TP because transport is vaguely relevant to a proposal. The program page is broad, but still bounded by transport physics. Be explicit that the research question depends on transport behavior.

Submitting with nonstandard routing

The official route conditions are explicit. Misrouting is one of the fastest ways to create delays or disqualifications.

Missing standard program context

Although this opportunity page is short, it references NSF 24-1 and PAPPG. Ignoring those instructions and treating it as a generic narrative exercise is a compliance risk.

Underdeveloped collaboration structure

If including industry or multi-site partners, state roles and interfaces. Transport projects often span instrumentation, data collection, and integration. Undefined responsibility can weaken credibility.

Overpromising commercialization claims

TP is fundamentally research-oriented. Translational framing helps, but claims should remain tied to evidence that can be supported within project scope.

Review expectations and proposal quality signals

In competitive NSF engineering programs, review quality often hinges on a few recurring signals:

• clarity of mechanism-driven innovation,
• consistency between problem statement and objectives,
• plausibility of method and validation,
• and institutional readiness to carry out the full project.

For TP specifically, reviewers also respond well to proposals that make transport pathways explicit across scales. If your model claims an effect at one scale and your validation is only at a higher or different scale, state that boundary transparently.

It helps to include an explicit “evidence hierarchy” section in your internal draft:

1. primary measurements,
2. derived transport metrics,
3. uncertainty bounds,
4. and implications for performance outcomes.

That structure mirrors what reviewers look for in transport-heavy proposals: not only novelty, but verifiable, scalable understanding.

Strategic preparation cycle for a continuous submission program

Because the page does not publish a single due date, teams should define internal milestones. A realistic 10-week model:

• Weeks 1–2: confirm alignment to TP topics and NSF route.
• Weeks 3–4: draft abstract, objectives, and scientific rationale.
• Weeks 5–6: build experimental/computational design and data strategy.
• Weeks 7–8: construct budget, compliance attachments, and reviewer-ready tables.
• Week 9: internal review by a non-team member and program office.
• Week 10: route-check, proofread, and submit.

Running two internal submission cycles per year improves odds in open-window programs because each wave can leverage new feedback without waiting for an external cycle.

FAQ

Is this a deadline-based solicitation?

The official page for Transport Phenomena lists upcoming due dates as “full proposal accepted anytime.” There is no fixed short-cycle deadline shown in the summary.

Is there a published award amount?

No fixed amount, minimum award, or single max amount is published on the page. If you need budget planning references, verify if any partner notices or annual program notes provide benchmarks.

Does this require Grants.gov submission?

For the program page as currently presented, it says proposals cannot currently be submitted through Grants.gov. Use Research.gov/NSF 24-1 routing as the stated path.

Who can I contact for submission questions?

The page lists [email protected] as the TP Program Team contact.

Is this suitable for 2026–2027 applicants?

Yes. It is posted in 2026 and supports ongoing proposals. That is why many teams use it as part of FY2026–FY2027 planning cycles.

Official links and next actions

• Program page: https://www.nsf.gov/funding/opportunities/transport-phenomena
• Program guidelines (PD path): https://www.nsf.gov/funding/opportunities/transport-phenomena/pd26-366y (official page path reference)
• Proposal framework: https://www.nsf.gov/funding/opportunities/transport-phenomena (NSF 24-1 context and routing)
• PAPPG: https://www.nsf.gov/policies/pappg/
• Research.gov: https://www.research.gov/
• NSF Grants and award terms: https://www.nsf.gov/awardsearch/showAward

For teams using this opportunity, the practical rule is simple: treat the open window as a benefit for planning, not an excuse for weak execution. The program supports serious transport science with clear scope discipline, strong mechanism-to-impact logic, and strict adherence to NSF submission rules.