The correct answer is 3.52 h. A marathon covers 26.2 miles, which equals about 42.16 km. At a constant 12 km/h, the runner covers that distance in 42.16 ÷ 12 ≈ 3.51–3.52 hours, so 3.52 h is the matching choice. The other options come from unit slips: 2.18 h ignores the mile-to-kilometer distance, and 3.14 h mixes kilometers per hour with miles. Only 3.52 h survives the check.

The Conversion Mechanism Behind the Answer

The whole problem hinges on one conversion factor. One mile equals 1.609344 kilometers exactly. Multiplying 26.2 miles by that factor gives 42.16 km, and the marathon's official distance traces back to that figure. World Athletics and course certifiers treat 42.195 km as the standard, so 26.2 miles is a rounded label for 42.195 km. The 42.16 km figure comes from the rounded 26.2, and the difference is 35 meters, which is negligible at this speed.

Once distance is in kilometers, constant speed turns the calculation into simple division. Time equals distance divided by speed, so 42.195 ÷ 12 = 3.516 hours, or 3 hours 31 minutes. That is the pure physics answer under the assumption of no stops and no pace variation.

The unit check is where most people go wrong. Kilometers per hour can only divide into kilometers, so a runner holding 12 km/h must first convert miles. Skipping that step produces answers that look plausible but are dimensionally wrong. A quick mental check: 26.2 miles is close to 42 km, and 42 divided by 12 is 3.5, so anything near 2.2 or 5.3 hours signals a conversion error.

The constant-speed assumption deserves a note. Real runners do not hold a fixed pace for three and a half hours. Speed varies with terrain, fueling, and fatigue, and the average speed over the race is what determines finish time. The question asks only about the ideal case, which is why the arithmetic works cleanly.

Quantified Context: What 3.52 Hours Means in Racing Terms

Three hours and 31 minutes is a serious recreational marathon time. It corresponds to a pace of roughly 8:03 per mile, or 4:59 per kilometer. That puts a runner near the faster end of age-group fields. Most marathon finishers cluster between 4 and 5 hours, so a 3:31 finish typically lands in the top third of a large race.

The numbers also expose the gap between flat arithmetic and real racing. A runner who averages 12 km/h on a flat training run will usually slow on race day, so an honest prediction needs a small buffer. Course elevation, weather, and crowding at aid stations each add time that constant-speed math cannot capture.

Here is how the answer choices compare, along with the likely error behind each.

Choice Value Status Likely error
2.18 h 2.18 h Wrong Treated 26.2 as km and divided by 12
3.14 h 3.14 h Wrong Mixed miles with km/h, or multiplied instead of dividing
3.52 h 3.52 h Correct Converted miles to km, then divided by speed
5.3 h 5.3 h Wrong Used mph figure against km distance, or a slow-pace slip

The table makes the diagnostic pattern clear. Every wrong choice is a unit-management failure, not a misunderstanding of the physics. Students who write the units beside each number catch these errors before they commit.

Edge Cases That Shift the Real Answer

The 3.52-hour figure assumes a perfectly measured course, which is true for certified races. Certified marathon courses are measured along the shortest possible path, so runners who drift wide around corners run farther than 42.195 km. On a twisty course, a runner can cover an extra 0.2 to 0.5 km without noticing, adding roughly one to three minutes at 12 km/h.

Temperature and humidity move the number more. Exercise physiology guidance from major sports medicine bodies notes that heat raises heart rate and slows sustainable pace, often by 3 to 8 percent in warm conditions. At 12 km/h that drag could add 6 to 17 minutes across the race. Cold, wind, and rain produce smaller but real penalties.

Elevation is the other major lever. A hilly course can cost several minutes per significant climb. The Boston Marathon's net descent is famous for helping some runners while punishing others with muscle damage on the downhills. Constant speed ignores these gradients entirely.

There is one counterintuitive detail worth flagging. A runner who holds a constant velocity for 3.52 hours can break the marathon down into a sequence of short splits, but the actual race is governed by energy availability rather than velocity. Glycogen depletion near the 30 km mark often forces a slowdown that no steady-state model predicts. The constant-speed answer is a benchmark, not a forecast.

Misconceptions That Produce the Wrong Choices

The most common mistake is confusing miles and kilometers in the numerator. Dividing 26.2 by 12 gives 2.18, which is exactly the first distractor, and that is no accident. Test makers expect students to forget the conversion under time pressure.

The reverse slip is dividing a kilometer distance by a miles-per-hour speed, or the mirror image. These mismatches produce the 3.14 and 5.3 figures. None of them represent a real runner's time; they represent arithmetic done on inconsistent units.

A second misconception is that speed and time scale linearly across distances. They do, mathematically, but human physiology breaks linearity. A runner who runs a 10K at a given pace cannot hold that pace for a full marathon without training that specifically supports it. The formula is exact; the biological assumption is not.

A third error treats the rounded 26.2 as exact. The true marathon distance is 26.219 miles, or 42.195 km, which adds about 20 seconds at this pace. Negligible for a multiple-choice test, meaningful if you are chasing a personal best.

Forgetting the mile-to-kilometer conversion is the single biggest cause of wrong answers. Dividing by 12 without checking units lets 2.18 h slip through as a plausible choice. Assuming a constant race pace overstates real performance for untrained runners. Using a rounded distance of 26.2 instead of 42.195 km slightly understates the time. Confusing average speed with instantaneous speed during a race misleads prediction.

Practical Actions: Reproducing and Extending the Calculation

The calculation takes under a minute if you follow a fixed sequence. First, convert the race distance to kilometers. Second, divide by the speed in km/h. Third, sanity-check the result against a rough estimate. This pipeline works for any distance and any speed, not just the marathon case.

Follow these thresholds when checking your work. A marathon is about 42 km, so at 12 km/h the answer must sit near 3.5 hours. At 10 km/h it should sit near 4.2 hours, and at 15 km/h near 2.8 hours. If your result falls far outside the expected band, a conversion error is almost certainly present.

For race-day planning, add a buffer to the pure answer. Most coaches suggest adding 3 to 5 percent to a predicted time to account for imperfect execution. Applied to 3.52 hours, that yields 3.37 to 3.70 hours, or roughly 3 hours 37 minutes to 3 hours 42 minutes of realistic expectation at that fitness level.

If you want a more honest model, track your actual splits over several long runs. Average those split speeds and use the average in the formula. This accounts for fatigue and fueling failures that constant-speed math hides, and it turns the benchmark into a usable forecast.

Limitations of the Constant-Speed Model

The constant-speed model is exact for physics and approximate for people. It says nothing about fatigue, fueling, weather, or terrain, all of which move real finish times by minutes. Treat 3.52 h as the answer to the question asked, not as a promise to any runner.

The rounding in 26.2 miles introduces a small error, and the unit conversion introduces a slightly larger one if done carelessly. Neither changes the correct multiple-choice option. What changes real outcomes is the gap between a mathematical speed and a sustainable racing pace.

For any decision tied to health, training, or race-day safety, the arithmetic here is general information rather than personal guidance. Consult a qualified coach or sports medicine professional before making training or racing decisions, especially if you have underlying health conditions.