Nobody does this division in their head. Highway engineers keep a conversion chart taped to the wall or — more likely — let the CAD file handle it. A bridge at station 1,247+35 (that's 124,735 feet from the project origin) sits at milepost 236.24. The formula is (124,735 ÷ 5,280) + some offset because the project zero and the route zero are different places. That offset changes from project to project. Get it wrong and the bridge goes in the wrong county.
Surveyors avoid the division altogether during fieldwork. They measure everything in decimal feet. The total station is set to feet. The data collector records feet. The traverse closes in feet. Only at the end, when someone writes the legal description, does the total get divided by 5,280 — once — and rounded. The surveyor writes "thence N 45° E a distance of 2,640.00 feet (0.50 miles)." The feet are the measurement. The miles are the translation.
Runners know the landmarks, not the formula. A tenth of a mile is 528 feet. A quarter mile is 1,320 feet — one lap of a standard track. A half mile is 2,640. Most people who run regularly can feel a quarter mile in their legs. They don't think "1,320 feet." They think "one lap." The foot count is for the course certifier with the calibrated bicycle.
If you need a quick estimate without a calculator: 1,000 feet is roughly 0.19 miles. 5,000 feet is a hair under a mile — 0.947, to be exact. A football field from goal line to goal line is 300 feet, which is about 0.057 miles. You'd need about 17.6 football fields to make a mile. None of these are round numbers. None of them will ever be round numbers. The 5,280-foot mile guarantees it.
Why 5,280? The number that no committee would ever choose
The mile began as the Roman mille passus — literally "a thousand paces." A Roman pace was two steps, roughly 5 Roman feet, giving a mile of about 5,000 Roman feet. As the Roman Empire receded and local measurement customs took over, medieval England developed the furlong: 660 feet, the distance a team of oxen could plough a furrow before needing rest. An acre was the area ploughed in one day — 1 furlong long by 1 chain (22 yards, or 66 feet) wide. When Elizabeth I's parliament standardized the statute mile in 1593, they defined it as 8 furlongs. Since a furlong was already fixed at 660 feet, the mile became 8 × 660 = 5,280 feet. The number was inherited from oxen and ploughs, not from any mathematical consideration.
The furlong-chain-rod system was brilliantly self-consistent for surveying: 1 furlong = 10 chains = 40 rods = 660 feet. An acre = 1 furlong × 1 chain = 43,560 square feet — a number that still appears on every US property deed. The statute mile of 5,280 feet was the only number in the system not divisible by 10, and it was the one that mattered most for travel. The metric system, when it arrived in the 1790s, fixed this by defining the kilometer as exactly 1,000 meters — a number a committee would choose.
The international foot vs. the survey foot: a 2 ppm problem that survived 64 years
In 1959, the United States and the British Commonwealth signed the International Yard and Pound Agreement, which defined 1 yard = 0.9144 meter exactly, making 1 international foot = 0.3048 meter exactly. But the US had previously defined its foot as 1,200/3,937 meter (≈ 0.3048006096 meter) — the "US survey foot." The difference is tiny: about 2 parts per million, or 0.01 foot per mile. For most purposes, that's invisible. For state plane coordinate systems — which express coordinates in millions of feet — that 2 ppm grows to several feet of horizontal displacement, enough to shift a property line on a large plat.
NIST formally deprecated the US survey foot on January 1, 2023, after 64 years of maintaining dual definitions. Twenty-three states had already legislated the switch; several more had survey-foot coordinates baked into decades of GIS layers. The practical rule: any survey plat dated before 2023 must be checked for which foot it used. The difference between the two feet over 1 mile of road is about 0.01 foot — negligible. Over the 300-mile length of a state, it's about 3 feet — enough to put a highway centerline in the wrong lane.
Aviation: feet up, miles across — and they never meet
Aviation is the one domain where feet and miles coexist on the same chart without ever converting between them. Altitude is in feet above mean sea level (MSL) or above ground level (AGL). Horizontal distances on instrument approach plates are in nautical miles (NM), not statute miles. A typical ILS approach might call for a decision altitude of 200 feet AGL and require 1/2 statute mile visibility — the pilot sees both numbers on the same plate but never multiplies one by the other. The conversion that pilots do use is feet-per-minute descent rate against groundspeed in knots: a 3° glideslope requires about 318 feet per nautical mile, which at 120 knots groundspeed works out to roughly 636 feet per minute. That conversion uses 6,076 feet per nautical mile — not 5,280.
Air traffic control separates aircraft vertically by 1,000 feet (or 500 feet under reduced vertical separation minima below FL290). Horizontally, separation is 3 to 5 nautical miles. No controller converts between the two — the units measure orthogonal dimensions that never interact arithmetically. The only place feet-to-statute-miles matters in aviation is on the sectional chart's scale bar.
Quick reference
| Feet | Miles | |
|---|---|---|
| 528 | 0.1 | Manhattan block (~20 per mile) |
| 1,320 | 0.25 | Standard track lap |
| 2,640 | 0.5 | Half mile |
| 5,280 | 1 | The statute mile |
| 10,000 | 1.894 | Typical general aviation runway |
| 13,200 | 2.5 | 5K race (actually 3.107 mi) |
| 26,400 | 5 | 10K training run |
| 69,168 | 13.1 | Half marathon |
| 138,336 | 26.2 | Marathon |
| 250,000 | 47.35 | Low Earth orbit (~250K ft) |
Frequently Asked Questions
How do I convert feet to miles?
Divide by 5,280. miles = feet ÷ 5,280. Use the calculator at the top of this page — doing this division by hand produces a 42-digit repeating decimal and you will make a rounding error eventually. For quick estimates, 1,000 feet ≈ 0.19 miles; 5,000 feet ≈ 0.95 miles.
Why does 1/5280 produce such an ugly decimal?
5,280 factors into 2⁵ × 3 × 5 × 11. For a fraction to produce a terminating decimal, the denominator's prime factors can only be 2 and 5. The 3 and the 11 guarantee the decimal repeats forever. The 11 is the worst contributor — it gives the 2-digit "09" repeating block you see in 0.0001893939... The 3 stretches the overall period to 42 digits.
What's the difference between the international foot and the US survey foot in miles?
The international foot (0.3048 m exactly, since 1959) and the US survey foot (1200/3937 m, the pre-1959 definition) differ by about 2 parts per million. Over one mile (5,280 ft), the survey-foot mile is about 0.01 ft longer — negligible for a milepost. Over a 300-mile state boundary, the difference is about 3 feet. NIST deprecated the survey foot in 2023. When working with legacy surveys, always verify which foot was used.
Why don't runners think in feet when measuring distance?
Because feet are too small for human-scale distance. 5,280 of anything is hard to count. Runners use miles (or kilometers) because the numbers stay small — a 10K is 6.2 miles, which is 32,808 feet, a number nobody wants on a race bib. The foot only reappears at the track: 1,320 feet to the quarter mile, measured by the course certifier with a steel tape and a calibrated bicycle, certified to the nearest inch. The rest of us just run the oval.
Do pilots convert feet to statute miles?
Almost never. Altitude is in feet (MSL or AGL), horizontal distance is in nautical miles, and the two dimensions don't interact arithmetically. The conversion pilots do use is feet-per-minute descent rate to groundspeed in knots, which uses nautical miles (6,076 ft/NM), not statute miles (5,280 ft/mi). The only place statute miles appear in the cockpit is on the visibility minimum of an approach plate — and that's a look-up, not a calculation.
Engineering Context
Station equations. A highway's stationing baseline runs in feet from a project origin. Mileposts run in miles from a route origin — typically the state line. The two don't start at the same place, and they can run in opposite directions. A station equation — "Sta 1247+35.20 = MP 236.24" — reconciles them. The contractor reads this on the plans, multiplies 236.24 by 5,280 to get feet, then adjusts for the offset. If the sign is wrong — if the station runs north-to-south and the milepost runs south-to-north — the bridge lands a mile from where it should be. The arithmetic is simple. Getting the sign right is where people fail.
In road design, vertical curves are computed in feet (stationing along the centerline) while speed limits and sight distances are in miles per hour. The two meet in stopping sight distance formulas: SSD = 1.47 × V × t + V² / (30 × (a/32.2)), where V is in mph and the output is in feet. The conversion factor 1.47 converts mph to feet per second — 5,280 ft/mi ÷ 3,600 s/hr. That 5,280 appears in the denominator of every highway design equation that bridges speed and distance. Length Conversion Guide.
More: miles to feet · miles to meters · feet to meters · km to miles · Guide