Knots to Feet per Second Converter - Convert knots to ft/s
Accurate knots to feet per second (ft/s) converter with exact nautical and SI constants, worked steps, expanded reference tables, rounding rules, detailed FAQs, tips, and structured data.
Exact identity: ft/s = knots × 11575/6858 (≈ 1.687809857). Reverse: knots = (ft/s) × 6858/11575 (≈ 0.5924838013). See all MetricCalc's online speed calculators.
About Knots to Feet per Second Conversion
Knots are the lingua franca of aviation and maritime operations, because a knot equals one nautical mile per hour and nautical miles are baked into charts and procedures. Feet per second (ft/s) appears in U.S. instrumentation, legacy archives, and some facility tests. This converter implements the exact identity so your public numbers in ft/s align perfectly with nautical-context data.
Treat m/s as your canonical compute unit; derive knots or ft/s at presentation. Round once at output to keep values stable across dashboards, APIs, and time.
Knots to Feet per Second Formula
Exact relationship
Use either expression:
ft/s = knots × 11575/6858 (≈ 1.687809857)
// inverse
knots = (ft/s) × 6858/11575 (≈ 0.5924838013)Definition chain:
1 nautical mile = 1852 m (exact)
1 hour = 3600 s (exact)
1 ft = 0.3048 m (exact)
⇒ ft/s = knots × (1852/3600) ÷ 0.3048 = knots × 11575/6858 (exact)Related Speed Converters
What are Knots?
A knot equals one nautical mile per hour. Because nautical miles are defined exactly and align with Earth-reference navigation (lat/long), knots remain the standard in aviation and marine communication. The unit is SI-traceable through its meter and second components.
Reporting in knots keeps operational data intuitive for pilots and mariners, while exact identities ensure your conversions to ft/s remain audit-ready.
What is Feet per Second (ft/s)?
Feet per second expresses the number of feet traveled in one second. It is common in U.S.-centric datasets, ballistics and sports timing, and certain engineering reports. Converting from knots to ft/s uses a fixed rational factor (11575/6858), making synchronization with customary-unit requirements straightforward.
When publishing outward-facing numbers in ft/s, include a brief methodology note (constants, rounding policy, and anchors) to streamline reviews and audits.
Step-by-Step: Converting knots to ft/s
- Read the speed in knots.
- Multiply by 11575/6858 to obtain ft/s.
- Apply a single rounding step aligned to your policy or device precision.
- Label units explicitly in legends, labels, and column headers.
Example walkthrough:
Input: 120 kn
Compute: ft/s = 120 × (11575/6858)
Output: ≈ 202.5371829 ft/s (UI rounding only)Common Conversions
| 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 |
Quick Reference Table
| 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 |
Precision, Rounding & Significant Figures
Operational rounding
Preserve full internal precision through calculations and round once at presentation. Scientific notation helps with extreme magnitudes; never overwrite stored values with rounded UI numbers.
Consistent documentation
Publish constants, the inverse, and example anchors alongside your export schema. Use explicit unit-suffixed field names (speed_knots, speed_fps, speed_ms) and include a tiny CI suite to validate both directions continuously.
Where This Converter Is Used
- Navigation overlays converting flight or marine speeds to U.S. customary units.
- Aviation/marine telemetry pipelines reconciling nautical reporting with ft/s requirements.
- Wind-tunnel, CFD, and facility reports for audiences that expect ft/s alongside knots.
- Compliance and safety documents with exact constants and transparent rounding rules.
Frequently Asked Questions
What is the exact formula to convert knots to feet per second?
Because 1 knot = 1 nautical mile per hour, with 1 nautical mile = 1,852 m (exact) and 1 hour = 3,600 s, and 1 ft = 0.3048 m (exact), we have ft/s = knots × (1852/3600) ÷ 0.3048 = knots × (11575/6858) exactly (≈ 1.687809857 × knots). The reverse is knots = (ft/s) × 6858/11575.
Is 11575/6858 an exact factor?
Yes. It’s a rational number derived from exact definitions (nautical mile, meter, second, and foot). No approximation is involved until you choose how many decimals to display.
Why are knots standard in aviation and marine contexts?
Knots tie directly to nautical miles per hour, which aligns with nautical charts and navigation conventions. This makes situational awareness and chart calculations intuitive for pilots and mariners.
Which unit should I store in my database: knots, ft/s, or m/s?
Store meters per second (m/s). Convert to knots or ft/s at presentation boundaries. Centralize constants and round once at output to prevent discrepancies across systems.
What rounding policy should I use for public dashboards or compliance reports?
Keep full internal precision and round once at presentation based on your sensor resolution or policy. Document this policy near constants and examples for auditability.
Can I enter scientific notation inputs like 1.8e2 to represent 180 knots?
Yes. The calculator accepts common numeric forms, including scientific notation. For extreme magnitudes the display switches to scientific notation automatically.
What anchor values are useful for QA?
1 kn ≈ 1.687809857 ft/s; 10 kn ≈ 16.87809857 ft/s; 100 kn ≈ 168.7809857 ft/s. Reverse: 1 ft/s ≈ 0.5924838013 kn; 100 ft/s ≈ 59.24838013 kn.
Is this conversion linear across all ranges?
Yes. Speed conversions are linear. Scaling the input in knots scales the output in ft/s by a fixed constant (11575/6858).
Where do knots → ft/s conversions appear?
Navigation overlays, avionics exports, marine telemetry, and wind-tunnel or CFD reports needing U.S. customary units for certain audiences.
Does locale formatting change the stored value?
No. Locale only affects how numbers are displayed; the stored values and arithmetic remain exact. Apply locale formatting at render time.
Any mental-math shortcuts for quick checks?
Multiply knots by ~1.69 to estimate ft/s. For software, use the exact 11575/6858 factor and round once at presentation.
How should I label fields in exports and APIs?
Use explicit unit-suffixed names like speed_knots, speed_fps, and speed_ms. Include a short methodology note with constants, inverse, rounding policy, and anchor conversions.
Tips for Working with knots & ft/s
- Use m/s as the compute base; render knots or ft/s at the edge.
- Round once at output; avoid multiple rounding stages across the pipeline.
- Publish constants and anchors; run round-trip checks in CI to catch regressions early.
- Keep unit symbols explicit throughout labels, legends, and export headers.