NSF 25-510: Coupling, Energetics, and Dynamics of Atmospheric Regions (CEDAR)

NSF 25-510: Coupling, Energetics, and Dynamics of Atmospheric Regions (CEDAR)

Coupling, Energetics, and Dynamics of Atmospheric Regions (CEDAR) is a recurring U.S. NSF Geosciences program for research teams that study how the atmosphere and near-space regions interact across altitudes, energy pathways, and coupling processes. It is one of the few NSF lines that explicitly calls for work spanning the middle atmosphere, thermosphere, ionosphere, and exosphere while explicitly rewarding projects that combine observations, modeling, and open-science-compatible methods.

If your group is building a proposal that needs atmosphere-ionosphere links, geospace processes, cross-disciplinary data integration, or planetary-comparison insights that can strengthen terrestrial interpretation, this is an opportunity worth tracking. The solicitation is active and open to annual target dates, with a target deadline pattern in March and an upcoming 2027 cycle date aligned with the first Wednesday of March. It is a program-level entry point with broad applicant categories but clear research scope.

Key details at a glance

What CEDAR actually covers

CEDAR is not a broad “science in atmosphere” program; it is a focused upper-atmosphere portfolio. The solicitation describes a mission around atmospheric regions from the middle atmosphere upward through thermosphere, ionosphere, and exosphere, with special attention to coupling dynamics, energy transfer, chemistry, and both internal and external drivers. This includes lower atmosphere perturbations that propagate upward and solar/radiation or particle inputs from above.

The strongest proposals are usually those that are not only scientifically sound but also clearly systems-oriented. A good CEDAR concept often does three things:

1. Defines a cross-region coupling question with evidence that it cannot be addressed from single-layer observations alone.
2. Integrates theory/modeling and observations in a way where each informs the other.
3. Shows a path from immediate output to reusable, externally useful scientific value.

The program explicitly encourages AI and machine learning methods, as well as open data and open science practices. That does not mean you must claim deep AI novelty or provide a complete software stack if it is not the project driver. It means your approach should be evidence-based and reflect modern analysis norms where appropriate. In review, “AI/ML token compliance” without concrete value-add can actually hurt: reviewers and program staff are typically looking for fit between problem, method, and observability.

From the program language, CEDAR also includes comparative aeronomy studies of planetary atmospheres where directly relevant to Earth, so this is one route for projects that blend terrestrial and planetary contexts.

Who this opportunity is for

The solicitation includes a broad applicant structure for a scientifically technical program:

• U.S. Institutions of Higher Education, including community colleges and other accredited two- or four-year IHEs acting on behalf of faculty.
• Nonprofit non-academic organizations, including U.S. museums, observatories, research labs, professional societies, or similar entities tied to education or research.
• For-profit U.S. organizations, including small businesses, that have strong scientific or engineering research capacity and an interest in innovation.
• Federally recognized Tribal Nations.

The program states no PI restrictions. That means principal investigators are evaluated on proposal merit and suitability rather than strict PI class caps beyond the common NSF submission limits.

For planning this is important: CEDAR is often suitable not only for traditional university-led proposals but also for mixed teams where instrument groups, computing teams, or observatory partners can contribute substantive science and data work. If you are at a for-profit with strong observational modeling integration and a research mission, you are not automatically excluded.

Common fit profiles include:

• Faculty with an active portfolio in upper atmosphere modeling, ionospheric/geomagnetic coupling, or space weather-related chemistry.
• Early-career-led groups trying to formalize collaborative pipelines between field observations and simulation.
• Institutions with instrument access or data-sharing pathways that can be scaled into proposal-level evidence.
• Teams that can show student and early-career scientist participation as part of the training and delivery model.

Reviewers in this track generally prefer concrete scientific progression: what is the core coupling hypothesis, what new observations/modeling are needed, what will the project change, and why this should advance existing CEDAR and geospace understanding rather than just replicate prior work.

Funding profile and what reviewers expect

This program lists an estimated annual funding amount of $3,000,000 pending availability and typically 10 to 15 awards. The solicitation clarifies that normal awards are around 1–5 years with a typical figure of about $150,000 per year and no explicit F&A cap in the section surfaced for this solicitation text. There is no allowance for voluntary committed cost sharing.

The budget language matters strategically. Because there is no mandated fixed amount per award, the key is coherent budget justification tied to scope. NSF reviewers will still question unrealistic multi-year scaling, especially if methodology and data pathways are not proportional to requested budget. A better proposal demonstrates:

• A lean core experimental/computational plan anchored by explicit questions.
• Clear milestones across year 1, year 2, and optional extension phases.
• Budget aligned to deliverables that match personnel, computing, and data requirements.
• Evidence of realistic publication and dissemination plans.

Given NSF practices, projects with ambiguous deliverable chains or broad wish lists often lose. Use budget tables as proof of execution logic, not just line costs.

What to submit and where

NSF gives two supported routes:

• Research.gov
• Grants.gov

For collaborative proposals, the solicitation requires Research.gov submission. That matters for teams with multiple institutions from the outset.

The solicitation also states letters of intent and preliminary proposals are not required. Submissions require full proposals only. That lowers front-end overhead but increases pressure on the core application quality because you lose the early feedback cushion many people expect from concept-level pre-screens.

When submitting in this program, use the required framing:

• Proposal title starts with “CEDAR:”.
• Follow current NSF Proposal & Award Policies & Procedures Guide.
• Use the NSF Grants.gov or Research.gov package requirements precisely.
• Ensure the sponsoring institution can complete signatures and submission steps on time.

For 2027-cycle planning, practical submission notes:

• Start application drafting at least 6–8 weeks before the March target date.
• Keep a dedicated submission calendar with both local time and server timezone references because Research.gov/grants.gov validation behavior is sensitive.
• Build in a buffer for pre-check/post-check issues; NSF recommends starting submission at least five business days before deadline.

Because the target deadline is recurring, it is easy to underestimate annual drift. “March 05, 2025” shown in one block of the solicitation should be read as the pattern anchor (first Wednesday in March annually), meaning 2027 timing will be different by calendar year. Treat each posted target date as binding for that cycle.

Preparation strategy for a competitive CEDAR proposal

1) Define one coupling story and avoid broadness

Good CEDAR proposals are not broad geospace essays. They are about a specific coupling process with measurable outputs. A strong central question might ask why transport and energy transfer in a defined region pair behaves differently across seasons, geomagnetic conditions, or model classes. Avoid three independent scientific islands in one proposal. If your project has two major objectives, connect them through one mechanism.

A practical tactic is to write one “single-sentence mechanism model” at the start of your science narrative:

• Input (perturbation from lower atmosphere/solar/particle source)
• Intermediate coupling (transport, chemistry change, dynamical response)
• Observable signature (instrument output/model residual)
• Hypothesis test (what data/model output proves or refutes)

2) Build observation-model coupling explicitly

The solicitation context rewards projects that use both observations and modeling. Your narrative should be explicit on which observations anchor model assumptions and where models test missing data or predict unobserved behaviors.

Avoid generic language such as “observations will be compared with simulations.” Instead define:

• What parameter, resolution, and cadence are required.
• What uncertainty metric will evaluate success.
• Which model components are being constrained and which are exploratory.

3) Use AI/ML and open science where they help, not as decoration

AI/ML is encouraged but not mandatory for every proposal. If included, explain whether it improves forecasting, data cleaning, anomaly detection, feature extraction, or cross-platform integration. If ML is added only for trend optics, you risk negative credibility.

Open data practices should be tied to reproducibility and reuse. NSF and the broader geoscience ecosystem are increasingly explicit about transparency, so include versioning, metadata standardization, and release intent where possible.

4) Plan reviewer-friendly structure

A reviewer reading a large proposal at 11 p.m. values clarity. Use simple structure:

• Problem statement linked to CEDAR goals.
• Specific annual and per-phase milestones.
• Clear evidence for why your team is uniquely positioned.
• Realistic risk controls (if one data source fails, what is the fallback science path).

5) Show training and capacity value

The program’s broader framing includes early-career engagement and broader participation. Even if training is not your headline, include concrete student roles, postdoc responsibilities, or cross-institution workforce development in the project plan. That is consistent with typical NSF review culture and supports impact logic.

Common mistakes and how to avoid them

• Ignoring the annual recurring nature of target dates. Some teams prepare as if only one static date exists; this causes confusion when internal calendars assume a fixed date.
• Using a proposal title that does not follow required prefix conventions. This is avoidable but frequently fatal if caught late in compliance checks.
• Submitting full proposals with weak submission mechanics. No LOI helps lower overhead but increases risk if full proposals are rushed.
• Over-promising data scope without integration design. “We will use many instruments” without fusion logic leads to weak scoring.
• Weak open-science treatment. If you claim open-data practices, include practical steps.
• No collaborative route planning. If your team has multiple organizations, use Research.gov from the start.

FAQ

Is this open for 2026/2027 submissions?

CEDAR is a recurring program with annual target dates. The solicitation indicates an annual target date cadence and lists the first Wednesday in March as the recurring pattern. On the public page this was reflected as a 2027 target date context with March timing, which is consistent with this cadence.

Is the deadline in 2026 still open?

The page content includes both historical posting context and annual target framework. Given your 2026/2027 target-year requirement, treat this as a recurring opportunity for the current annual cycle, with the March target date as the operational deadline for each cycle.

Can for-profits apply?

Yes, U.S.-based commercial organizations with qualifying research/engineering capacity can submit in this program.

Can a for-profit partner submit alone?

Yes if eligible and eligible activity scope is strong, but the strongest proposals usually show robust scientific partnerships and a defensible execution strategy.

Is cost sharing required?

No. Voluntary committed cost sharing is explicitly prohibited.

Are PI restrictions likely to limit us?

The solicitation says there are no PI restrictions, but there is still a limit on proposals per PI/co-PI (2 per target date).

What is required for submission systems?

Submit via Research.gov or Grants.gov. For collaborative proposals, the route should be Research.gov. You still need to follow full NSF preparation and award instructions and include the required program-specific requirements.

Practical application timeline (recommended)

Because this is a target-date program with recurring annual windows, a practical internal schedule for a CEDAR entry can be:

• T-12 to T-10 weeks: finalize team, define scientific hypothesis, map open-data and observatory sources.
• T-10 to T-6 weeks: draft concept, budget, and risk matrix; start internal technical review.
• T-6 to T-4 weeks: finalize proposal with all sections, verify institutional readiness for Research.gov/Grants.gov pathway.
• T-4 to T-2 weeks: run internal compliance and formatting pass; confirm title starts with CEDAR; secure all signatures/administrative clearances.
• T-2 weeks onward: begin submission prep early; allow for pre-check corrections.
• T-5 business days: complete submission attempt to cover re-submissions.

That timeline is defensive and significantly increases submission quality.

What evidence helps this proposal stand out

• Strong coupling diagram with region-to-region transfer pathways.
• Pilot data showing that your team can process and combine observations across platforms.
• A realistic computing plan with uncertainty handling.
• A publication and release plan for outputs.
• Early-career participation plan with explicit mentorship responsibilities.

Even when technical innovation is strong, proposals fail if execution proof is weak. Build execution proof directly into proposal text.

Official links and references

• NSF program page: https://www.nsf.gov/funding/opportunities/cedar-coupling-energetics-dynamics-atmospheric-regions/
• NSF solicitation: https://www.nsf.gov/funding/opportunities/cedar-coupling-energetics-dynamics-atmospheric-regions/nsf25-510/solicitation
• Related filing and submission systems: Research.gov and Grants.gov via official NSF workflow pages

Notes on submission fit for your planning

This is a good fit if your team’s science naturally sits at the interface of atmosphere, ionosphere, and space environment. It is less ideal if your question is purely one-layer, purely engineering, or only loosely linked to coupling dynamics. In those cases the same work may have a better home in a targeted computational, instrumentation, or programmatic opportunity.

For teams that qualify, use this cycle as a chance to move from concept into a tightly executed research pipeline. CEDAR rewards work that can be explained in plain scientific terms, implemented with technical discipline, and delivered with measurable milestones.