Rocket thrust from mass flow
Multiply how much propellant leaves each second by how fast it leaves to get thrust: 100 kg/s at 3000 m/s gives 300000 N, the ideal figure for engine sizing and propulsion homework. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Mass flow rate
- 100
- Exhaust velocity
- 3,000
- Mdot
- 100
- Ve
- 3,000
- Thrust
- 300,000
- Thrust N
- 300,000
Rocket and jet engine thrust is the force that accelerates a vehicle by expelling propellant rearward. In the ideal, constant-exhaust model used in textbooks and first-pass mission design, thrust equals the product of propellant mass flow rate and effective exhaust velocity: F equals ṁ times ve. This rocket thrust from mass flow calculator accepts those two quantities in SI units—kilograms per second and metres per second—multiplies them, and returns force in newtons so you can size engines, check homework, or feed a spreadsheet without unit mistakes. Zero flow or zero velocity correctly yields zero thrust.
What F = ṁ · ve means for rocket thrust
In rocket propulsion the vehicle gains momentum by ejecting mass at high relative speed. For a steady exhaust stream with effective exhaust velocity ve, the rate of momentum leaving the engine is the product of how much mass leaves per unit time and how fast that mass leaves relative to the vehicle. That momentum flux is the thrust force: F equals ṁ times ve.
Effective exhaust velocity folds nozzle exit speed, pressure imbalance at the exit plane, and related losses into a single equivalent speed so that the simple product matches the net axial force. When mass flow is expressed in kilograms per second and ve in metres per second, F is in newtons—exactly the SI force unit used in trajectory codes and structural load cases.
Specific impulse Isp relates to the same family through ve equals Isp times g0, so if you already know Isp you can convert to ve first and then use this calculator; conversely, given thrust and ṁ you can back out ve as F divided by ṁ.
What you can do with it
Homework and propulsion class checks
Students submit mass flow (kg/s) and effective exhaust velocity (m/s) and verify thrust in newtons against textbook F=ṁ·ve worked examples.
Mission design and engine trades
Mission notebooks convert candidate ṁ and ve pairs into thrust for first-pass stage sizing before detailed nozzle or Isp tables.
Test-stand and dashboard cross-checks
Ground-test software multiplies measured propellant flow by effective ve to cross-check load-cell thrust under the ideal product model.
FAQ
How is rocket thrust calculated from mass flow?
Ideal thrust is F = ṁ · ve: multiply propellant mass flow rate (kg/s) by effective exhaust velocity (m/s). The product is force in newtons in SI units.
What happens if mass flow or exhaust velocity is negative?
Negative mass flow or negative effective exhaust velocity is rejected; zero is allowed and yields zero thrust.
How does this relate to specific impulse?
Effective exhaust velocity ve equals Isp times standard gravity g0. Convert Isp to ve first, then use F = ṁ · ve, or supply ve directly if you already have it.
Can mass flow or exhaust velocity be zero?
Yes. Zero is accepted for either value and gives zero thrust, which is handy for a coast phase when the engine is off. Only negative values are refused, because they would produce a meaningless force.
How do I find exhaust velocity from a known thrust?
Divide the thrust by the mass flow. For example, 300000 newtons produced with 100 kilograms of propellant per second means an effective exhaust velocity of 3000 metres per second.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/astro/thrust-from-mass-flow \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"mass_flow_rate":100,"exhaust_velocity":3000}'const res = await fetch("https://api.kit.forhosting.com/astro/thrust-from-mass-flow", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"mass_flow_rate": 100,
"exhaust_velocity": 3000
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/astro/thrust-from-mass-flow",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"mass_flow_rate": 100,
"exhaust_velocity": 3000
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/astro/thrust-from-mass-flow", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"mass_flow_rate":100,"exhaust_velocity":3000}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"mass_flow_rate":100,"exhaust_velocity":3000}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/astro/thrust-from-mass-flow", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"mass_flow_rate": 100,
"exhaust_velocity": 3000
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "astro.thrust_from_mass_flow",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Negative mass flow or negative exhaust velocity is rejected with invalid_input rather than a silent absurd force.
What F = ṁ · ve means for rocket thrust
This endpoint implements only the product: you supply ṁ and ve, and you receive F with formula and unit labels so the result is self-documenting in logs and UI.
Input contract, units, and error behaviour
Zero is allowed for either input and produces zero thrust, which is useful for coast phases and edge-case tests. Example: ṁ equals one hundred kilograms per second and ve equals three thousand metres per second yields three hundred thousand newtons. POST a JSON body with two required finite numbers: mass_flow_rate (aliases mdot, m_dot, mass_flow, propellant_flow) in kilograms per second, and exhaust_velocity (aliases ve, v_e, v_exhaust, effective_exhaust_velocity) in metres per second. Each field may arrive as a JSON number or as a numeric string; missing fields, empty strings, and non-finite values fail with invalid_input naming the field. On success the body echoes the cleaned mass_flow_rate and mdot, exhaust_velocity and ve, thrust and thrust_N (identical numeric values), a formula string F = ṁ · ve, an equation string substituting your numbers, a units object labelling kg/s, m/s, and N, and a short message restating the SI product. Failed validation is not billed; successful calls use the published $0.002 base price.
Where a mass-flow thrust API earns its keep
Aerospace students and MOOC platforms need a deterministic oracle for the F equals ṁ ve identity so homework and auto-graders do not argue over unit conversions or silent acceptance of negative inputs. Keep requests small, pin the rounded thrust in tests, and you get reproducible newtons for LMS plugins, edge workers, and design sketches without standing up a full propulsion simulation stack of your own. Early mission studies and spreadsheet-driven engine trades often start from a target thrust and a candidate exhaust velocity, then solve for required mass flow—or the reverse—before opening detailed nozzle tables; a tiny parse API avoids reimplementing validation in every notebook. Propulsion labs and ground-test dashboards can stream measured mass flow and inferred ve into this endpoint to cross-check load-cell thrust within the ideal model before applying corrections for ambient pressure and instrumentation bias.
Technical questions
What units should I use for mass flow and exhaust velocity?
Use kilograms per second for mass_flow_rate and metres per second for exhaust_velocity. Then thrust is returned in newtons (N).
What does the rocket thrust from mass flow calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.