Triangles You Can't Solve With Basic Right-Angle Math
Most people learn sine and cosine in the context of right triangles, which makes sense because that's where they're taught. But real-world geometry rarely gives you a clean 90-degree angle to work with. That's where the Law of Sines and Law of Cosines come in, and honestly, they're not as intuitive as textbooks make them look. The Law of Sines states that the ratio of a side length to the sine of its opposite angle is constant across all three sides of any triangle. Written out, it looks like a/ sin(A) = b/ sin(B) = c/ sin(C). The Law of Cosines is essentially the Pythagorean theorem generalized for non-right triangles: c² = a² + b² - 2ab·cos(C). They're not interchangeable. Pick the wrong one for your given information and you'll waste time or hit an impossible calculation.
Law Of Sines Law Of Cosines
Here's the practical rule I follow every time: if you have an angle-side pair and need another angle or side, use the Law of Sines. If you're working with two sides and the included angle (SAS) or three sides (SSS), the Law of Cosines is your starting point. Everything else is just algebra from there. I ran into a specific problem a few years back working on a surveying project where I needed to determine the distance between two points on opposite sides of a river. I had two baseline measurements from my position to each point and the angle between those baselines. That's a textbook SAS setup, so Law of Cosines was the obvious choice. The tricky part came after: I needed one of the other angles to triangulate a third point, and I almost used the Law of Sines without checking a boundary condition. The sine of the angle I was solving for came out slightly greater than 1 due to rounding in my intermediate calculations. The calculator just gave me an error, and I lost about twenty minutes before I realized I'd carried too few decimal places through the first step. The workaround was to recompute the side length using the Law of Cosines with full precision from the start, then back-calculate the angle. Never round intermediate values when working between these two laws. Keep at least six significant figures until your final answer. The Law of Sines has what's called the ambiguous case, and it catches people off guard regularly. When you're given two sides and a non-included angle (SSA), there can be zero solutions, one solution, or two valid solutions for the triangle. The condition depends on the relationship between the side opposite the given angle and the height of the triangle (the adjacent side times the sine of the given angle). If the opposite side is shorter than that height, no triangle exists. If it's equal, one right triangle exists. If it's longer but still shorter than the adjacent side, two different triangles are possible. This isn't theoretical — I've seen engineering students miss the second valid triangle and design a component that physically couldn't assemble.
For the Law of Cosines, there's a common misconception that it's only useful for finding a missing side. It's actually the more reliable law for finding angles when you have all three sides, because the cosine function is one-to-one across the 0-to-180-degree range of triangle angles. The Law of Sines, on the other hand, returns an acute angle from the arcsine function even when the actual angle is obtuse. You have to manually check whether the angle should be 180 minus the calculator's result. With the Law of Cosines, the sign of the cosine tells you immediately whether the angle is acute or obtuse. Positive cosine means acute, negative means obtuse. That's a significant practical advantage in SSS problems. Both laws break down in edge cases. The Law of Sines becomes numerically unstable when an angle approaches 0 or 180 degrees because the sine values are very close together and small differences in side lengths produce wildly different angle results. In those near-degenerate triangles, the Law of Cosines is far more stable. The Law of Cosines itself doesn't have the ambiguous case, but it requires knowing either the included angle for SAS or all three sides for SSS. If you're given two sides and a non-included angle, you're forced into the Law of Sines and its associated complications. When I need to solve a triangle programmatically, I use a decision tree. Check what information is given first. Two angles and any side — Law of Sines immediately. Two sides and the included angle — Law of Cosines for the third side, then Law of Sines for one of the remaining angles. Three sides — Law of Cosines for one angle, then Law of Cosines again for a second angle to avoid the ambiguous case entirely. Two sides and a non-included angle — Law of Sines, but test for the ambiguous case by comparing the opposite side against the adjacent side times the sine of the given angle. That last one is where most mistakes happen, and it's also the only case where you should explicitly check for two possible solutions rather than assuming a single answer.
Get the Full Details
