Return the distance you calculated as a float with 13 decimals.

Nooooooooooooooo!

It is perfectly acceptable to require accuracy of 13 decimals ( though it's a bit many ), but do not specify anything that could be construed as rounding or truncating.

Read this and go forth and sin no more.

ETA: You didn't learn, did you?

Duplicate: https://github.com/Codewars/content-issues/wiki/List-of-Possible-Duplicate-Kata#haversine-distance

there are weird assumptions in the task, imo...

• we are to considere actual globe/sphere
• but wind direction isn't given compared to the plane expected destination, and rather... I actually have no idea how it's given. Direction according to what? North? That should be clearly specified.
• we are assuming that the wind never changes of direction during the flight. Which is... weird. Not really a problem, but not natural either (especially if you imagine a complete circle around earth x) ). Would be better to just say it too.

• Heading must be in degrees and rounded to a whole number between 0 and 360. I believe this doesn't apply anymore => to remove
• It would be better to have an additional section describing quickly what the outputs are (types, units, ...). For now, I needed to scan the description 2 times to find the unit for the flight time. Same for the inputs, actually ("angle toward north", ...)

Should not the radius of the earth be specified in appropriate precision?

Duplicate.