Skip to main content

In Hatchet by Gary Paulsen, why does the moose attack Brian?

That's what Brian wants to know, too, in Chapter 16 when he feels that the moose has attacked him for no reason at all. It's senseless, he thinks, and insane for the moose to have charged him:



So insane, he thought, letting sleep cover the pain in his chest—such an insane attack for no reason and he fell asleep with his mind trying to make the moose have reason. 



Long after this incident, Brian continues to think of the moose attack as something crazy, something that could not be explained rationally by finding a cause for it. Even after he gets home and is able to research the things he didn't know during his time in the wilderness, like the real name ("grouse") of the creatures he'd called "foolbirds," he still doesn't know why the moose had attacked him.


Brian does accept, however, that nature's power is sometimes random and cruel. That's what he learned from the moose attack as well as the tornado that hit his shelter while he was still recovering from the damage the animal had inflicted on him.


Still, as readers, we're curious to understand why the moose did attack. Surely it wasn't just for fun, and surely the enormous moose didn't feel threatened by Brian's small arrow that he was using to find food at the time, right? The novel provides no answers. But if you Google why female moose like the one in the story do attack, you'll learn that they are extremely protective of their calves. If the moose in the story had her calf nearby, she might have attacked Brian even though he didn't provoke her. (Her intention may have been to demonstrate to Brian that he'd better not even think about getting close to the moose calf!) In fact, because female moose are known for being so protective and defensive, this discussion from SurvivalGrounds.com indicates that in Canada, female moose are responsible for more human deaths than even the grizzly bear.

Comments

Popular posts from this blog

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes."  He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear.  Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...