Feet per Second to Knots Converter - Convert ft/s to knots
High-quality feet per second (ft/s) to knots converter using exact identities from SI and nautical definitions, with step-by-step examples, expanded tables, rounding guidance, detailed FAQs, practical tips, and structured data.
Exact identity: knots = (ft/s) × 6858/11575 (≈ 0.5924838013). Reverse: ft/s = knots × 11575/6858 (≈ 1.687809857). See all MetricCalc's online speed calculators.
About Feet per Second to Knots Conversion
Feet per second (ft/s) is common in U.S. telemetry archives, sports timing, and facility tests. Knots dominate aviation and marine reporting because a knot directly references nautical miles per hour, which ties neatly to navigation. This converter implements the exact identity between ft/s and knots so your values stay reproducible across dashboards, PDFs, and CSV exports.
Best practice: keep m/s as the canonical compute unit. Derive ft/s or knots at presentation boundaries and round once at output. This prevents subtle drift as numbers flow across services and devices.
Feet per Second to Knots Formula
Exact relationship
Use either expression:
knots = (ft/s) × 6858/11575 (≈ 0.5924838013)
// inverse
ft/s = knots × 11575/6858 (≈ 1.687809857)Definition chain:
1 ft = 0.3048 m (exact)
1 nautical mile = 1852 m (exact)
1 hour = 3600 s (exact)
⇒ knots = (ft/s × 0.3048) ÷ (1852/3600) = (ft/s) × 6858/11575 (exact)Related Speed Converters
What is Feet per Second (ft/s)?
Feet per second indicates the number of feet traveled in one second. It persists in legacy datasets (aerospace tests, sports performance), where U.S. customary units are entrenched. Converting to knots is linear, using a fixed rational factor derived from SI and nautical definitions.
Typical magnitudes include walking (< 15 ft/s), urban traffic (~60–100 ft/s), and wind-tunnel peaks (> 150 ft/s). The same constant 6858/11575 applies across the entire range.
What are Knots?
Knots measure speed in nautical miles per hour. Because nautical charts and navigation conventions are historically based on nautical miles, knots remain the standard in aviation and maritime operations. One knot equals exactly 1,852 meters per hour divided by 3,600 seconds, which ties conversions to SI.
Using knots ensures immediate comprehension for aviators and mariners while staying auditable thanks to exact unit identities.
Step-by-Step: Converting ft/s to knots
- Read the speed in ft/s.
- Multiply by 6858/11575 to obtain knots.
- Round once at presentation; preserve full internal precision.
- Apply the same display rule across UI, exports, and PDFs.
Example walkthrough:
Input: 100 ft/s
Compute: knots = 100 × (6858/11575)
Output: ≈ 59.24838013 kn (UI rounding only)Common Conversions
| Feet per Second (ft/s) | Knots |
|---|---|
| 1 | 0.5924838013 |
| 5 | 2.962419006 |
| 10 | 5.924838013 |
| 25 | 14.81209503 |
| 50 | 29.62419006 |
| 100 | 59.24838013 |
| 150 | 88.87257019 |
| 200 | 118.4967603 |
| 300 | 177.7451404 |
| 500 | 296.2419006 |
Quick Reference Table
| Knots | Feet per Second (ft/s) |
|---|---|
| 1 | 1.687809857 |
| 5 | 8.439049286 |
| 10 | 16.87809857 |
| 20 | 33.75619714 |
| 30 | 50.63429571 |
| 50 | 84.39049286 |
| 80 | 135.0247886 |
| 100 | 168.7809857 |
| 120 | 202.5371829 |
| 200 | 337.5619714 |
Precision, Rounding & Significant Figures
Operational rounding
Convert with full internal precision and round once at presentation. Use scientific notation for very small or very large values when helpful; keep the underlying numbers exact for reproducibility and audits.
Consistent documentation
Use explicit unit-suffixed fields (speed_fps, speed_knots, speed_ms). Publish a short methods note listing exact identities (“knots = (ft/s) × 6858/11575”), the inverse, and a clear display policy. Add a small CI test set to validate both directions.
Where This Converter Is Used
- Aviation and marine dashboards that standardize public reports in knots.
- UAV testing and flight summaries correlating legacy ft/s feeds with nautical reporting.
- Wind-tunnel studies and CFD post-processing where audiences expect knots.
- Compliance exports requiring explicit constants and one-time rounding.
Frequently Asked Questions
What is the exact formula to convert feet per second to knots?
A knot is one nautical mile per hour. By definition 1 nautical mile = 1,852 m (exact) and 1 hour = 3,600 s. Also, 1 ft = 0.3048 m (exact). Therefore knots = (ft/s × 0.3048) ÷ (1852/3600) = (ft/s) × (6858/11575) exactly, which is ≈ 0.5924838013 × (ft/s). The inverse is ft/s = knots × (11575/6858) (≈ 1.687809857).
Are these factors exact or approximations?
They’re exact because they derive from exact definitions: 1 ft = 0.3048 m exactly and 1 nautical mile = 1,852 m exactly. Chaining those with 3,600 s per hour yields rational factors 6858/11575 and 11575/6858 without rounding.
Should I use knots or kmph in public-facing dashboards?
Use whichever your audience expects. Aviation and marine audiences expect knots; road traffic dashboards often use kmph. Keep your canonical compute unit in m/s, then derive ft/s, knots, or kmph at presentation time.
Which unit should I store in my database?
Store meters per second (m/s). It minimizes chained conversions and aligns with SI. Derive ft/s or knots for display, and round once at output to avoid silent divergence across systems.
How should I round values for dashboards, CSV exports, or reports?
Keep full internal precision and round once at presentation. Choose decimals that match sensor resolution or policy (e.g., 1–2 decimals for consumer dashboards; more for engineering). Document this policy next to constants and examples.
Can I type scientific notation like 1.2e2 into the calculator?
Yes. The input accepts common numeric forms including scientific notation. Extremely small or large results automatically switch to scientific notation to preserve readability and significant figures.
What anchor values should I memorize or add to CI tests?
1 ft/s ≈ 0.5924838013 kn; 10 ft/s ≈ 5.924838013 kn; 100 ft/s ≈ 59.24838013 kn. Reverse: 1 kn ≈ 1.687809857 ft/s; 100 kn ≈ 168.7809857 ft/s.
Is the conversion linear across all magnitudes?
Yes. Speed conversions are linear. Doubling ft/s doubles knots; the proportionality constant 6858/11575 is fixed for all magnitudes.
Where do ft/s → knots conversions show up in practice?
Aviation and marine telemetry, UAV test sheets, wind-tunnel studies with nautical reporting, and mixed-unit pipelines that must present speeds to maritime or aviation audiences.
Does locale formatting affect the underlying value?
No. Locale only changes how numbers look (separators and decimal symbols). The stored values and conversions remain exact. Apply locale formatting at render time.
Is a knot different from a nautical mile per hour?
They’re identical: 1 knot = 1 nautical mile per hour by definition. It is not the same as statute miles per hour (mph).
Any mental-math tips for quick estimation?
Multiply ft/s by ~0.59 to estimate knots. For software and compliance documents, use the exact rational factor 6858/11575 and round once at presentation.
How should I label fields in exports and APIs?
Use explicit unit-suffixed names such as speed_fps, speed_knots, and speed_ms. Include a methods note listing identities, the inverse, rounding policy, and a few anchor conversions.
Tips for Working with ft/s & knots
- Prefer m/s as the compute base; render ft/s or knots at presentation edges.
- Round once at output; never feed rounded UI numbers back into storage.
- Publish constants and anchors; validate both directions continuously in CI.
- Keep unit symbols explicit across legends, labels, and export headers.