Skip to content
Campus Alert Archive
Oregon

All-clear after crash at 11th and Franklin

AI-generated · every claim is source-linked
ORotheremergency notificationhigh confidence

UO Alert posted an all-clear that a motor vehicle crash at E. 11th Ave and Franklin Blvd had been removed. The initial crash product was not on the live alerts index this pass and is not invented.

Alerts
1
Response
—
Killed
—
Injured
—
Institution
University of Oregon
Public R1 · OR
All Oregon cases →
UO Alert
Official alert policy
Read when and how Oregon says it will use UO Alert: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

1 message in sequence · 1 verified verbatim

Confirmed wording is transcribed character-for-character from a primary source. Use Verify this quote under each message to open that source in a new tab and compare the text yourself.

ALL CLEARWebsite
Verified verbatim196 chars
April 3, 2026, 6:26 PM The motor vehicle crash at E. 11th Ave and Franklin Blvd has been removed. Watch for any remaining emergency responders. Any additional updates will be at alerts.uoregon.edu
Dual independent HTML fetch 2026-08-24 of Drupal body. Second blind sha256 821182bcc014919cbb85978cf19f15d2192c6d999a9d80315364484f15b51266.
All-clear-only live item; initial not invented. Thread N/A (web posting, not X).
Distinct incident from 2025-12-11-university-of-oregon-franklin-orchard-armed-robbery (different year, type, and Franklin block).
Message elements

How the first alert is built

To check this alert, SuperGrok Heavy 4.5 (an AI) read it in full 25 separate times, independently. Each read decided whether the message answers each of the six questions and gave a short reason. A final reviewer then weighed all 25 and wrote the plain-English verdict you see when you open a row. The score (for example 22/25) is how many reads agreed; the 25 individual reads are tucked underneath if you want to check them.

April 3, 2026, 6:26 PM The motor vehicle crash at E. 11th Ave and Franklin Blvd has been removed. Watch for any remaining emergency responders. Any additional updates will be at alerts.uoregon.edu

  • Sourceabsent0/25

    Final assessment

    No branded sender in the Drupal all-clear body. Majority 0/25.

    Who is sending the alert and who is responding. People act faster on a message from a clearly identifiable, credible sender, such as a named department, the police, or a branded alert system, than on an anonymous notice. A branded signature counts.

    See all 25 individual reads
    1. absent: No branded UO Alert tag appears; the body opens with a date then the crash all-clear (UO MVC AC, pass 1).
    2. absent: Source is absent in this Drupal body (UO MVC AC, pass 2).
    3. absent: I code S 0 because the sender is not identified (UO MVC AC, pass 3).
    4. absent: A date line is not a source signature (UO MVC AC, pass 4).
    5. absent: I mark S absent (UO MVC AC, pass 5).
    6. absent: The crash all-clear never says who is sending it (UO MVC AC, pass 6).
    7. absent: Source fails (UO MVC AC, pass 7).
    8. absent: I score S 0 (UO MVC AC, pass 8).
    9. absent: No UOPD or UO Alert colon tag is in the text (UO MVC AC, pass 9).
    10. absent: I find no branded signature (UO MVC AC, pass 10).
    11. absent: S is 0 on this all-clear (UO MVC AC, pass 11).
    12. absent: alerts.uoregon.edu is a URL not a sender brand (UO MVC AC, pass 12).
    13. absent: I will not treat a URL as Source (UO MVC AC, pass 13).
    14. absent: No police agency is named (UO MVC AC, pass 14).
    15. absent: Source element is missing (UO MVC AC, pass 15).
    16. absent: I read no sender identity (UO MVC AC, pass 16).
    17. absent: Without UO Alert Eugene in this body, Source is absent (UO MVC AC, pass 17).
    18. absent: I do not import twitter:title brand into the product (UO MVC AC, pass 18).
    19. absent: S absent (UO MVC AC, pass 19).
    20. absent: Named crash location is location not source (UO MVC AC, pass 20).
    21. absent: I code source absent (UO MVC AC, pass 21).
    22. absent: Sender identity is unspecified (UO MVC AC, pass 22).
    23. absent: S 0 (UO MVC AC, pass 23).
    24. absent: The all-clear does not name who is sending it (UO MVC AC, pass 24).
    25. absent: No agency byline appears (UO MVC AC, pass 25).
  • Hazardpresent25/25

    Final assessment

    Motor vehicle crash is a specific named event. Majority 25/25.

    What the threat actually is. A complete warning names the specific danger, such as a shooter, a fire, a tornado, or a gas leak, rather than a vague emergency, because people decide what to do based on what they are facing.

    See all 25 individual reads
    1. present: Hazard is a motor vehicle crash, a specific named event (UO MVC AC, pass 1).
    2. present: The text says motor vehicle crash (UO MVC AC, pass 2).
    3. present: H is present via motor vehicle crash (UO MVC AC, pass 3).
    4. present: I count H 1 (UO MVC AC, pass 4).
    5. present: Crash is a specific event, not a generic incident (UO MVC AC, pass 5).
    6. present: I mark H present (UO MVC AC, pass 6).
    7. present: Named hazard: motor vehicle crash (UO MVC AC, pass 7).
    8. present: H holds (UO MVC AC, pass 8).
    9. present: The body names the crash (UO MVC AC, pass 9).
    10. present: I score H 1 for motor vehicle crash (UO MVC AC, pass 10).
    11. present: A crash is a specific event (UO MVC AC, pass 11).
    12. present: Hazard element is satisfied (UO MVC AC, pass 12).
    13. present: I read motor vehicle crash as the hazard (UO MVC AC, pass 13).
    14. present: H is 1 (UO MVC AC, pass 14).
    15. present: The all-clear still names the crash (UO MVC AC, pass 15).
    16. present: Specific event language is present (UO MVC AC, pass 16).
    17. present: I find a named hazard (UO MVC AC, pass 17).
    18. present: Crash at 11th and Franklin is the event (UO MVC AC, pass 18).
    19. present: H present (UO MVC AC, pass 19).
    20. present: The product tells you what happened (UO MVC AC, pass 20).
    21. present: I treat crash as Hazard present (UO MVC AC, pass 21).
    22. present: Not a vague situation (UO MVC AC, pass 22).
    23. present: Hazard is the crash (UO MVC AC, pass 23).
    24. present: I code H 1 (UO MVC AC, pass 24).
    25. present: Motor vehicle crash is specific (UO MVC AC, pass 25).
  • Locationpresent25/25

    Final assessment

    E. 11th Ave and Franklin Blvd is a named intersection. Majority 25/25.

    Where the threat is. Saying whether danger is in a specific building, a part of campus, or area-wide lets people judge their own proximity and choose a safe direction. Without a where, a warning is hard to act on precisely.

    See all 25 individual reads
    1. present: Location is E. 11th Ave and Franklin Blvd, a named intersection (UO MVC AC, pass 1).
    2. present: The crash is at E. 11th Ave and Franklin Blvd (UO MVC AC, pass 2).
    3. present: L is present (UO MVC AC, pass 3).
    4. present: I count L 1 (UO MVC AC, pass 4).
    5. present: Named streets satisfy location (UO MVC AC, pass 5).
    6. present: I mark L present (UO MVC AC, pass 6).
    7. present: Where: E. 11th Ave and Franklin Blvd (UO MVC AC, pass 7).
    8. present: L holds (UO MVC AC, pass 8).
    9. present: I score L 1 (UO MVC AC, pass 9).
    10. present: An intersection is a place (UO MVC AC, pass 10).
    11. present: Location element is satisfied (UO MVC AC, pass 11).
    12. present: I read 11th and Franklin as location (UO MVC AC, pass 12).
    13. present: L is 1 (UO MVC AC, pass 13).
    14. present: The body names the intersection (UO MVC AC, pass 14).
    15. present: Street-level location is present (UO MVC AC, pass 15).
    16. present: I treat E. 11th Ave and Franklin Blvd as location (UO MVC AC, pass 16).
    17. present: Named place (UO MVC AC, pass 17).
    18. present: L present (UO MVC AC, pass 18).
    19. present: The crash site is specified (UO MVC AC, pass 19).
    20. present: I code L 1 (UO MVC AC, pass 20).
    21. present: Franklin Blvd plus 11th Ave is a location (UO MVC AC, pass 21).
    22. present: Where the crash was is named (UO MVC AC, pass 22).
    23. present: Location is not omitted (UO MVC AC, pass 23).
    24. present: I find a named intersection (UO MVC AC, pass 24).
    25. present: L 1 (UO MVC AC, pass 25).
  • Guidancepresent25/25

    Final assessment

    Watch for remaining emergency responders is an instruction. Majority 25/25.

    The protective action to take. A clear, specific instruction, such as shelter in place, evacuate, avoid the area, or run-hide-fight, drives faster and more correct protective behavior than describing the threat alone.

    See all 25 individual reads
    1. present: Guidance is Watch for any remaining emergency responders (UO MVC AC, pass 1).
    2. present: Watch for remaining responders is an instruction (UO MVC AC, pass 2).
    3. present: G is present (UO MVC AC, pass 3).
    4. present: I count G 1 (UO MVC AC, pass 4).
    5. present: The text tells people to watch for emergency responders (UO MVC AC, pass 5).
    6. present: I mark G present (UO MVC AC, pass 6).
    7. present: Watch for is cautionary guidance (UO MVC AC, pass 7).
    8. present: G holds (UO MVC AC, pass 8).
    9. present: I score G 1 (UO MVC AC, pass 9).
    10. present: An instruction remains after the crash is removed (UO MVC AC, pass 10).
    11. present: Guidance element is satisfied (UO MVC AC, pass 11).
    12. present: I read Watch for as guidance (UO MVC AC, pass 12).
    13. present: G is 1 (UO MVC AC, pass 13).
    14. present: The all-clear still instructs caution (UO MVC AC, pass 14).
    15. present: I treat Watch for remaining emergency responders as guidance (UO MVC AC, pass 15).
    16. present: Not merely status (UO MVC AC, pass 16).
    17. present: G present (UO MVC AC, pass 17).
    18. present: The product tells you what to do (UO MVC AC, pass 18).
    19. present: I code G 1 (UO MVC AC, pass 19).
    20. present: Cautionary watch language is guidance (UO MVC AC, pass 20).
    21. present: Recipients are instructed (UO MVC AC, pass 21).
    22. present: I find an instruction (UO MVC AC, pass 22).
    23. present: Guidance is Watch for remaining emergency responders (UO MVC AC, pass 23).
    24. present: I will count that as G (UO MVC AC, pass 24).
    25. present: G 1 (UO MVC AC, pass 25).
  • Timepresent25/25

    Final assessment

    April 3, 2026, 6:26 PM is a date and clock. Majority 25/25.

    When the message applies. A timestamp, the word now or immediately, or a phrase like until further notice tells the reader whether the danger is current and how quickly to act.

    See all 25 individual reads
    1. present: April 3, 2026, 6:26 PM is an explicit date and clock time (UO MVC AC, pass 1).
    2. present: T is present via April 3, 2026, 6:26 PM (UO MVC AC, pass 2).
    3. present: I count T 1 (UO MVC AC, pass 3).
    4. present: A clock time is listed in the rubric (UO MVC AC, pass 4).
    5. present: I mark T present (UO MVC AC, pass 5).
    6. present: The when is 6:26 PM April 3, 2026 (UO MVC AC, pass 6).
    7. present: T holds (UO MVC AC, pass 7).
    8. present: I score T 1 (UO MVC AC, pass 8).
    9. present: Date and clock are in the first line (UO MVC AC, pass 9).
    10. present: Time element is satisfied (UO MVC AC, pass 10).
    11. present: I read 6:26 PM as Time (UO MVC AC, pass 11).
    12. present: T is 1 (UO MVC AC, pass 12).
    13. present: A calendar date appears (UO MVC AC, pass 13).
    14. present: I treat April 3, 2026, 6:26 PM as Time present (UO MVC AC, pass 14).
    15. present: Without that stamp Time would fail (UO MVC AC, pass 15).
    16. present: T present (UO MVC AC, pass 16).
    17. present: Clock language is present (UO MVC AC, pass 17).
    18. present: I code T 1 (UO MVC AC, pass 18).
    19. present: The body names when (UO MVC AC, pass 19).
    20. present: I find a date and clock (UO MVC AC, pass 20).
    21. present: Time is 6:26 PM (UO MVC AC, pass 21).
    22. present: A date of the rubric kind is in the text (UO MVC AC, pass 22).
    23. present: I will count April 3, 2026 as Time (UO MVC AC, pass 23).
    24. present: T 1 (UO MVC AC, pass 24).
    25. present: Date plus clock is Time (UO MVC AC, pass 25).
  • Impactabsent0/25

    Final assessment

    No explicit injury or damage. Majority 0/25.

    What the hazard could do to the people in its path. Beyond naming the threat, a complete warning conveys its potential consequences or severity, such as that a tornado can level buildings or that a leak could be explosive, so recipients grasp how much danger they are in. Research on warning message content finds that a concrete impact statement helps people personalize their risk and act sooner.

    See all 25 individual reads
    1. absent: Impact is absent: the crash being removed does not state injury or damage (UO MVC AC, pass 1).
    2. absent: No deadly or injury language appears (UO MVC AC, pass 2).
    3. absent: I code I 0 (UO MVC AC, pass 3).
    4. absent: Watch for responders is guidance not impact (UO MVC AC, pass 4).
    5. absent: I mark I absent (UO MVC AC, pass 5).
    6. absent: The rubric example list is not matched (UO MVC AC, pass 6).
    7. absent: I find no harm sentence (UO MVC AC, pass 7).
    8. absent: Impact fails (UO MVC AC, pass 8).
    9. absent: I score I 0 (UO MVC AC, pass 9).
    10. absent: Naming a crash is the hazard, not impact (UO MVC AC, pass 10).
    11. absent: I 0 (UO MVC AC, pass 11).
    12. absent: Consequence language is missing (UO MVC AC, pass 12).
    13. absent: I decline to infer injuries (UO MVC AC, pass 13).
    14. absent: Impact is not present (UO MVC AC, pass 14).
    15. absent: I read no severity clause (UO MVC AC, pass 15).
    16. absent: Without harm language, Impact is absent (UO MVC AC, pass 16).
    17. absent: The all-clear does not state what the crash did (UO MVC AC, pass 17).
    18. absent: I code I absent (UO MVC AC, pass 18).
    19. absent: No injury is named (UO MVC AC, pass 19).
    20. absent: Impact element fails (UO MVC AC, pass 20).
    21. absent: I will not invent damage (UO MVC AC, pass 21).
    22. absent: I 0 on this all-clear (UO MVC AC, pass 22).
    23. absent: Crash removed is resolution not impact (UO MVC AC, pass 23).
    24. absent: I do not count a crash name as impact (UO MVC AC, pass 24).
    25. absent: Impact absent (UO MVC AC, pass 25).

Coded by SuperGrok Heavy 4.5

Systematic AI judgments with visible reasoning, not human-validated codings.

About this analysis
Context

Background

University of Oregon posts UO Alert products on safety.uoregon.edu/alerts.
Analysis

Key Findings

Official all-clear after a crash at E. 11th Ave and Franklin Blvd was removed.
Outcome
Crash removed. Watch for remaining emergency responders. All-clear-only record.
Provenance

Sources

Every claim on this page is meant to be checkable. Open the links below (and the Verify this quote control under each confirmed alert) to read the original university, news, or archive page yourself. Hostnames are shown so you can see where you are going; archived copies survive when live pages move or disappear. See also our methodology.

  1. Official
Cite this case

Campus Alert Archive. "University of Oregon: All-clear after crash at 11th and Franklin." Incident of April 3, 2026. Added August 2026. https://campusalertarchive.com/case/university-of-oregon-11th-franklin-crash-all-clear-2026-04-03/

Download case JSON

Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.

Tags
public-r1oregonuo-alertall-clear
Added August 2026Updated August 2026Via ingestion