The book does a startlingly good job of covering many areas of game programming that benefit from physics including projectiles, vehicles, and other solid bodies. Some more advanced concepts like fuel burnoff, body shape, and simulation in real time add to the usability of the book.
One of the biggest problems with the text is that if your going to jump into a single chapter and code up a sample of just the object being talked about your going to be okay. However, if your going to be deriving your own code and objects based on the material in the book your going to find yourself having a hard time.
A great example lies in the first chapter which derives formulas for working with a car, with a fuel tank and driver. Now, first off, the author implements 0 source code for the functions shown in the book. This leaves you as the reader to develop your own functions and test things out, possibly by adding another driver, or implementing a generic method for defining composite bodies. If your technically proficient enough to do this, you'll use the numbers provided to test your code. What do you find? Well, that the numbers the author put in the book are wrong.
Since the book is based on precise math and physics, this type of slip-up, especially in a prime example (its the major example for the first chapter), is killer in terms of my trust in the books content.
Still, I do recommend buying the book, just prepare yourself for the technical inconsistencies.