False reports, fabricated images, when you must help and when you merely may, and the standards nobody enforces.

In this lesson you will

  • State that knowingly false reports are criminal and explain what a fabricated report does.
  • Recognize fabricated and recycled storm imagery and apply basic checks.
  • Distinguish Good Samaritan immunity from a duty to rescue.
  • Apply the ethics of reporting, recording and victim dignity.
Standing note
General legal education, not legal advice. This module describes federal law that applies nationally and principles that apply broadly, and it deliberately avoids stating what any individual state requires, because that varies and it changes. Nothing here creates a lawyer-client relationship. For anything that turns on where you are standing, read your own state code or ask somebody qualified in your jurisdiction.

Lying is a crime and that is the least of it

Knowingly making a false report to law enforcement or emergency services is a criminal offense essentially everywhere, usually a misdemeanor and escalating sharply where it triggers a response that causes injury, or where it happens during a declared emergency. The specific offense and grading are state law and this lesson prints neither.

The larger harm is to the record
Module 7 lesson 1 explained that warnings are verified by reports, and module 10 lesson 2 showed the source field that weights them. A fabricated report verifies a warning that should not have verified, corrupts the archive every long-term statistic is drawn from, and spends the credibility that the words "trained spotter" carry. Documented incidents exist of falsified reports entering spotter networks and interfering with the warning process. It is not hypothetical.

Which extends to exaggeration, and this is the version that tempts decent people. Rounding a hail measurement up because it might help get a warning issued is the same act in a smaller coat. Module 5 lesson 5 showed that wind estimates already skew high and cluster on multiples of five; adding deliberate inflation to a known bias makes the record worse in a direction it was already leaning.

And on gaming a reliability score
This platform weights reports by the reporter's track record. Reporting what you think will score well rather than what you saw defeats the entire point of the score, and the honest report that says "funnel cloud, could not confirm ground contact from where I was" is worth more than a confident one that turns out to be wrong. The directive governing the national archive makes the same commitment: its purpose is to describe events accurately regardless of what that does to verification scores.

Images that are not what they claim

Module 10 lesson 6 gave the verification checks. Here is why they have become non-negotiable: fabricated storm imagery is now good enough to fool people and cheap enough to be everywhere. Forecast offices have had to publicly debunk viral images of tornadoes that never existed, and old footage recycled as live is a recurring pattern during every significant event.

  1. Reverse image search it. The single highest-yield check, and it catches almost all recycled material.
  2. Look at the metadata, if any survives. Upload date is not capture date.
  3. Look for the physics. Modules 3 and 4 taught you what these features look like. Generated images very often get the cloud base, the scale relationships or the debris wrong.
  4. Corroborate against radar. Module 9 taught you enough to ask whether there was even a storm there at the claimed time.
  5. Ask who, when and where, and treat an evasive answer as an answer.
And if you cannot verify it
You can still pass it on honestly, which is not the same as not passing it on. "Unverified image circulating, origin unknown, I cannot place it" is useful information for an office. Presenting it as an observation is the thing that is forbidden, and module 10 lesson 2 explained what it does to the source field when you do.

Helping

Two ideas that sound the same and are opposites, and conflating them is a documented failure mode.

Good Samaritan immunity
A shield. Every state has some version protecting somebody who voluntarily gives reasonable assistance in an emergency from being sued for it. It exists so that the fear of liability does not stop people helping.
A duty to rescue
An obligation. The general rule in the United States is that there is no legal duty to rescue a stranger, however unattractive that sounds. A small number of states impose some form of duty, and sources disagree about exactly which and how broadly, so this course names none.
Immunity is not a duty
Having a shield for helping does not mean you are required to help. Almost nobody has this the right way round. In most places the law does not compel you; what it does is remove a reason not to.

Two further points that are consistent across jurisdictions and are the practical guidance:

  • Once you start, do not abandon them worse off. A voluntary rescuer generally takes on a duty not to make the situation worse or to walk away leaving somebody in a worse position than they found them.
  • Calling 911 is almost always reasonable assistance, and it is frequently the most useful thing you can do. It is also the thing you are unambiguously competent to do.
The rule this course teaches
Call 911 first. Then help within your training and not beyond it. Module 8 established that a spotter who becomes a casualty has converted one problem into two. Somebody with first aid training should use it; somebody without should not attempt an extrication they have never practiced on a structure they cannot assess.

The part nobody enforces

Everything above has a legal edge. What follows does not, which is exactly why it is the last section of the last lesson of this course.

  • Accuracy beats speed. Being first with a wrong report is worse than being second with a right one, and the record keeps both.
  • Do not issue your own warnings. Not to followers, not to a neighborhood group. A competing unofficial warning confuses people during the minutes when confusion kills them, and module 1 lesson 7 showed how little trust the system has to spare.
  • Victims are people, not content. Filming an injured person is very rarely illegal and is frequently indefensible. The privacy law people invoke here mostly binds doctors and insurers rather than bystanders, which means the restraint has to come from you.
  • Credit other people's work. Somebody else's photograph is theirs, in law and in fairness.
  • Do not add to the convergence. Module 8 lesson 2 showed what a crowd does to a road network. The most ethical position on a bad day is often further away.
  • Your first duty is to the warning system, not to your audience, your channel, or your reputation.
The end of the course
Eleven modules, and what they are collectively for is one thing: to make you somebody whose report can be believed without being checked. Every threshold quoted verbatim, every bias explained, every "measured or estimated" tag, every instruction to report the time it happened rather than the time you called, exists to build that. The law sets a floor. What actually makes the system work is a few hundred thousand people choosing to be accurate when nobody would know if they were not.

Check yourself

You watched a funnel for two minutes and could not tell whether it reached the ground. You know a confirmed tornado report would improve your reliability score. What do you report?

  1. A funnel cloud, stating explicitly that you could not confirm ground contact from your position
  2. A tornado, since the funnel was clearly present and ground contact is usually implied
  3. Nothing, since you cannot be certain and an uncertain report is worse than none
  4. A funnel cloud, and a separate tornado report if anybody else in the area confirms one
Hint

Module 7 lesson 6 quoted a field guide phrase for exactly this situation.

Answer

A funnel cloud, stating explicitly that you could not confirm ground contact from your position

Report what you saw and say what you could not determine. Expressing uncertainty is information: it tells the forecaster how much to trust you, which is itself useful. The third option is wrong in the other direction, since a funnel cloud is a real and reportable observation, and the fourth would put your name on somebody else's observation, which module 10 lesson 2 covered.

Sources

  1. NWS Instruction 10-1605, Storm Data preparation
  2. Doswell, "Storm chasing with safety, courtesy and responsibility", the benchmark essay on chase ethics
  3. NWS Weather-Ready Nation, on false and inaccurate severe weather reports on social media
  4. NWS Weather Spotter's Field Guide