Skip to content
Campus Alert Archive
UMD

Follow-Up In Off-Campus Incident

AI-generated · every claim is source-linked
MDactive threattimely warninghigh confidence
Under Investigation

University of Maryland Police published a community notice on or about 2026-05-15. Full text is preserved from the official UMPD News archive.

Alerts
1
Response
—
Killed
0
Injured
0
Institution
University of Maryland, College Park
Public R1 · MD
All UMD cases →
~40,000 studentsUMPD Community Notice
Official alert policy
Read when and how UMD says it will use UMD Alerts: 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.

INITIAL ALERTEmail
Verified verbatim2403 chars
On May 15, 2026, at approximately 2:36 p.m., the University of Maryland Police Department responded to Lakeland Road and Rhode Island Avenue to assist the Prince George's County Police Department for the sound of gunfire. Once officers were on scene, information was gathered from a witness that verified the incident. While officers were still on scene, we were notified of incidents occurring in neighboring communities. At approximately 3:30 p.m., the Prince George's County Police Department shared information online about a critical incident and confirmed one person was in custody and one weapon was recovered after reports of shots fired in multiple locations in the northern portion of the county, to include the area of 67th Avenue and Patterson. At approximately 6:12 p.m., the Prince George's County Police Department held a press conference. During the press conference, it was confirmed that the suspect they had in custody was connected to the incident that occurred off-campus in College Park. The Prince George's County Police Department continues to investigate. Safety Resources: University of Maryland Police Department Emergency Number - 301-405-3333 / #3333 from a mobile phone (AT&T and Verizon Wireless) / 911 Non-Emergency Number - 301-405-3555 Prince George's County Police Department Emergency Number - 911 Non-Emergency Number - 301-352-1200 Office of Emergency Management and Business Continuity https://prepare.umd.edu/ for quick access to phone numbers and emergency guide UMD Guardian (Mobile Campus Safety App) https://umpdnews.umd.edu/download-umd-guardian-app-today UMD Police Walking Escort 301-405-3555 NITE Ride 301-314-3687 https://transportation.umd.edu/shuttle-um/nite-ride ADA/504 Coordinator 301-405-2841 https://accessibility.umd.edu/ Bias Incident Support Services 301-405-0980 https://biassupport.umd.edu/ BiasSupport@umd.edu Help Center (Peer Counseling & Crisis Intervention) 301-314-4357 https://helpcenterumd.org/ Counseling Center 301-314-7651 https://counseling.umd.edu/ CARE Office (Free & Confidential resource for those impacted by Sexual & Relationship Violence) 301-741-3442 https://health.umd.edu/CARE Health Center 301-314-8180 https://health.umd.edu/ Office of Civil Rights and Sexual Misconduct (OCRSM) 301-405-1142 TitleIXcoordinator@umd.edu https://ocrsm.umd.edu/ UMD Alerts https://alert.umd.edu
Transcribed from official umpdnews.umd.edu editor-content body.
Confirmed-verbatim recovery from live institutional source.
Message elements

How the first alert is built

To check this alert, Claude Opus 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.

On May 15, 2026, at approximately 2:36 p.m., the University of Maryland Police Department responded to Lakeland Road and Rhode Island Avenue to assist the Prince George's County Police Department for the sound of gunfire. Once officers were on scene, information was gathered from a witness that verified the incident. While officers were still on scene, we were notified of incidents occurring in neighboring communities. At approximately 3:30 p.m., the Prince George's County Police Department shared information online about a critical incident and confirmed one person was in custody and one weapon was recovered after reports of shots fired in multiple locations in the northern portion of the county, to include the area of 67th Avenue and Patterson. At approximately 6:12 p.m., the Prince George's County Police Department held a press conference. During the press conference, it was confirmed that the suspect they had in custody was connected to the incident that occurred off-campus in College Park. The Prince George's County Police Department continues to investigate. Safety Resources: University of Maryland Police Department Emergency Number - 301-405-3333 / #3333 from a mobile phone (AT&T and Verizon Wireless) / 911 Non-Emergency Number - 301-405-3555 Prince George's County Police Department Emergency Number - 911 Non-Emergency Number - 301-352-1200 Office of Emergency Management and Business Continuity https://prepare.umd.edu/ for quick access to phone numbers and emergency guide UMD Guardian (Mobile Campus Safety App) https://umpdnews.umd.edu/download-umd-guardian-app-today UMD Police Walking Escort 301-405-3555 NITE Ride 301-314-3687 https://transportation.umd.edu/shuttle-um/nite-ride ADA/504 Coordinator 301-405-2841 https://accessibility.umd.edu/ Bias Incident Support Services 301-405-0980 https://biassupport.umd.edu/ BiasSupport@umd.edu Help Center (Peer Counseling & Crisis Intervention) 301-314-4357 https://helpcenterumd.org/ Counseling Center 301-314-7651 https://counseling.umd.edu/ CARE Office (Free & Confidential resource for those impacted by Sexual & Relationship Violence) 301-741-3442 https://health.umd.edu/CARE Health Center 301-314-8180 https://health.umd.edu/ Office of Civil Rights and Sexual Misconduct (OCRSM) 301-405-1142 TitleIXcoordinator@umd.edu https://ocrsm.umd.edu/ UMD Alerts https://alert.umd.edu

  • Sourcepresent25/25

    Final assessment

    Present, 25 of 25: the account is issued in the university's voice and attributes the response to "the University of Maryland Police Department" alongside the Prince George's County Police Department.

    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. present: Attributes the account to the University of Maryland Police Department and county police.
    2. present: Written by the University of Maryland Police Department, which describes its own response.
    3. present: Repeatedly cites "the University of Maryland Police Department" as the responding and reporting agency.
    4. present: "the University of Maryland Police Department responded" names the issuing police agency directly.
    5. present: "The University of Maryland Police Department responded" identifies the issuing agency.
    6. present: The account is issued in the voice of the University of Maryland Police Department, which names itself throughout.
    7. present: Attributes the message to "the University of Maryland Police Department" and county police.
    8. present: Names the University of Maryland Police Department as responding and reporting agency.
    9. present: It names the "University of Maryland Police Department" and Prince George's County Police as responders and issuer.
    10. present: The University of Maryland Police Department is named as responding and reporting agency.
    11. present: Attributed to "the University of Maryland Police Department", working with county police.
    12. present: Attributed to the University of Maryland Police Department alongside Prince George's County Police.
    13. present: Attributed to the University of Maryland Police Department alongside the county police.
    14. present: Attributed throughout to the "University of Maryland Police Department" responding alongside county police.
    15. present: Attributes the account to the University of Maryland Police Department and the county police.
    16. present: The "University of Maryland Police Department" is named as responding and writing.
    17. present: It names the University of Maryland Police Department and Prince George's County Police as responders.
    18. present: "The University of Maryland Police Department responded" names the issuing agency clearly.
    19. present: The University of Maryland Police Department is named as responding and reporting agency.
    20. present: Names "the University of Maryland Police Department" and the Prince George's County Police as the responding authorities.
    21. present: It is written from the perspective of the University of Maryland Police Department, which is named repeatedly.
    22. present: The "University of Maryland Police Department" is named as responding and issuing agency.
    23. present: The "University of Maryland Police Department" and Prince George's County Police are named throughout as responders.
    24. present: Attributes the account to "the University of Maryland Police Department" and its county counterpart.
    25. present: The narrative is written by the University of Maryland Police Department, which describes its own officers responding.
  • Hazardpresent25/25

    Final assessment

    Present, 25 of 25: the message reports officers responding to "the sound of gunfire" and "reports of shots fired in multiple locations" in the northern county.

    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: Describes "the sound of gunfire" and "reports of shots fired in multiple locations".
    2. present: Reports "the sound of gunfire" and confirmed "shots fired in multiple locations".
    3. present: Describes "the sound of gunfire" and "reports of shots fired", a specific threat.
    4. present: It describes "the sound of gunfire" and "reports of shots fired in multiple locations".
    5. present: It names "the sound of gunfire" and "reports of shots fired", a specific threat.
    6. present: It reports "the sound of gunfire" and confirmed "shots fired in multiple locations", a specific threat.
    7. present: Describes "the sound of gunfire" and confirmed "shots fired in multiple locations".
    8. present: Describes "the sound of gunfire" and confirmed "shots fired in multiple locations".
    9. present: The text cites "the sound of gunfire" and "reports of shots fired in multiple locations".
    10. present: It reports "the sound of gunfire" and confirmed "shots fired in multiple locations", a specific threat.
    11. present: It reports "the sound of gunfire" and confirmed "shots fired in multiple locations".
    12. present: Describes "the sound of gunfire" and "reports of shots fired in multiple locations".
    13. present: Reports 'the sound of gunfire' and 'shots fired in multiple locations', a specific threat.
    14. present: Names "the sound of gunfire" and "reports of shots fired in multiple locations".
    15. present: Reports "the sound of gunfire" and later "shots fired in multiple locations", a specific threat.
    16. present: It reports "the sound of gunfire" and later "shots fired in multiple locations".
    17. present: The hazard is specific: "the sound of gunfire" and "reports of shots fired in multiple locations".
    18. present: The threat is "the sound of gunfire" and later "reports of shots fired in multiple locations".
    19. present: It describes "the sound of gunfire" and confirmed "reports of shots fired in multiple locations".
    20. present: Reports "the sound of gunfire" and later "shots fired in multiple locations", a specific threat.
    21. present: "The sound of gunfire" and confirmed "reports of shots fired" name a specific armed threat.
    22. present: It reports "the sound of gunfire" and "shots fired in multiple locations", a specific armed threat.
    23. present: The hazard is specific: "the sound of gunfire" and later "reports of shots fired in multiple locations".
    24. present: Describes "the sound of gunfire" and confirmed "shots fired in multiple locations", a specific threat.
    25. present: It names "the sound of gunfire" and "reports of shots fired in multiple locations", a specific weapons threat.
  • Locationpresent25/25

    Final assessment

    Present, 25 of 25: specific places are named, "Lakeland Road and Rhode Island Avenue" and "the area of 67th Avenue and Patterson", plus off campus College Park.

    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: Names "Lakeland Road and Rhode Island Avenue" and the area of 67th Avenue and Patterson.
    2. present: Names "Lakeland Road and Rhode Island Avenue" and the area of 67th Avenue and Patterson.
    3. present: Locates it at "Lakeland Road and Rhode Island Avenue" and near 67th Avenue and Patterson.
    4. present: It names "Lakeland Road and Rhode Island Avenue" and "67th Avenue and Patterson".
    5. present: It cites "Lakeland Road and Rhode Island Avenue" and the area of 67th Avenue and Patterson.
    6. present: Places are named, including "Lakeland Road and Rhode Island Avenue" and 67th Avenue and Patterson.
    7. present: Names "Lakeland Road and Rhode Island Avenue" and the area of 67th Avenue and Patterson.
    8. present: Cites Lakeland Road and Rhode Island Avenue plus 67th Avenue and Patterson.
    9. present: It specifies "Lakeland Road and Rhode Island Avenue" and the area of 67th Avenue and Patterson.
    10. present: It names "Lakeland Road and Rhode Island Avenue" and the area of 67th Avenue and Patterson.
    11. present: Places are named: "Lakeland Road and Rhode Island Avenue" and "67th Avenue and Patterson".
    12. present: Names "Lakeland Road and Rhode Island Avenue" and the area of 67th Avenue and Patterson.
    13. present: Cites 'Lakeland Road and Rhode Island Avenue' and the 67th Avenue and Patterson area.
    14. present: Specifies "Lakeland Road and Rhode Island Avenue" and the area of 67th Avenue and Patterson.
    15. present: Names "Lakeland Road and Rhode Island Avenue" and "67th Avenue and Patterson".
    16. present: It names "Lakeland Road and Rhode Island Avenue" and "67th Avenue and Patterson".
    17. present: It cites "Lakeland Road and Rhode Island Avenue" and "67th Avenue and Patterson".
    18. present: It cites "Lakeland Road and Rhode Island Avenue" and the area of 67th Avenue and Patterson.
    19. present: Places are specific: Lakeland Road and Rhode Island Avenue, and 67th Avenue and Patterson.
    20. present: Cites "Lakeland Road and Rhode Island Avenue" and the area of 67th Avenue and Patterson.
    21. present: It names "Lakeland Road and Rhode Island Avenue" and "the area of 67th Avenue and Patterson".
    22. present: Places are named, including "Lakeland Road and Rhode Island Avenue" and 67th Avenue and Patterson.
    23. present: It names "Lakeland Road and Rhode Island Avenue" and "the area of 67th Avenue and Patterson".
    24. present: Names "Lakeland Road and Rhode Island Avenue" and "67th Avenue and Patterson".
    25. present: Locations are named, including "Lakeland Road and Rhode Island Avenue" and "67th Avenue and Patterson".
  • Guidanceabsent0/25

    Final assessment

    Absent, 0 of 25: the message recounts a closed out response and lists safety and counseling phone numbers, but never tells readers to take any protective action.

    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. absent: It recounts the police response and lists contact resources but asks readers to do nothing protective.
    2. absent: It recounts police activity and lists resources but issues no protective instruction to readers.
    3. absent: It lists resource phone numbers but never tells recipients to take a protective action.
    4. absent: The message recaps police activity and lists resources; it never directs readers to take a protective action.
    5. absent: It lists resources and phone numbers but gives no protective action to take.
    6. absent: It only lists resources and phone numbers after the fact and never instructs readers to take a protective action.
    7. absent: It recounts what police did and lists phone numbers, but asks the reader to take no protective action.
    8. absent: It recounts what police did and lists resource numbers, but gives recipients no protective instruction.
    9. absent: Only contact numbers and support resources are listed; no protective action is asked of recipients.
    10. absent: The text recounts police actions and lists contact numbers but gives readers no protective instruction.
    11. absent: It lists support and contact resources afterward but directs no protective action to readers.
    12. absent: Only contact numbers and support resources are listed; recipients get no protective instruction.
    13. absent: It recounts what investigators did and lists resources, but gives recipients no protective instruction.
    14. absent: It recounts what police did and lists resource phone numbers, but instructs recipients to take no protective action.
    15. absent: It lists resource phone numbers but never tells readers to shelter, avoid, or otherwise act protectively.
    16. absent: The text only recounts police activity and lists resources; no protective action is asked of readers.
    17. absent: The message recounts police activity and lists resource phone numbers without instructing readers to take protective action.
    18. absent: The text narrates police actions and lists resources but never instructs readers to take a protective step.
    19. absent: It only recites what police did and lists resources; no protective action is asked of readers.
    20. absent: The body recounts police actions and lists resource phone numbers but directs no protective action to readers.
    21. absent: The message recounts police actions and lists resource numbers but never tells readers to take a protective action.
    22. absent: The text recounts police actions and lists support resources but never tells readers to take a protective action.
    23. absent: It recounts what police did and lists resource phone numbers, but gives recipients no protective action.
    24. absent: It narrates what police did and lists resource numbers, but gives readers no protective action.
    25. absent: It recounts what police did and lists contact resources, but gives recipients no protective action to take.
  • Timepresent25/25

    Final assessment

    Present, 25 of 25: events are timestamped precisely, "On May 15, 2026, at approximately 2:36 p.m.", then 3:30 p.m. and 6:12 p.m.

    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: Timestamps events precisely: approximately 2:36 p.m., 3:30 p.m., and 6:12 p.m. on May 15, 2026.
    2. present: Gives a detailed clock sequence including "approximately 2:36 p.m." and "approximately 6:12 p.m.".
    3. present: Gives precise times including "approximately 2:36 p.m." on May 15, 2026.
    4. present: Times are precise: "at approximately 2:36 p.m.", "At approximately 3:30 p.m.", "At approximately 6:12 p.m."
    5. present: Precise times appear: "at approximately 2:36 p.m." on May 15, 2026.
    6. present: Precise times are given: 2:36 p.m., 3:30 p.m., and a 6:12 p.m. press conference on May 15, 2026.
    7. present: Gives precise clock times, "at approximately 2:36 p.m." and "At approximately 6:12 p.m.".
    8. present: Timestamps the sequence, "at approximately 2:36 p.m." and later 3:30 p.m. and 6:12 p.m.
    9. present: Times are precise, including "May 15, 2026, at approximately 2:36 p.m." and 6:12 p.m.
    10. present: Precise times are given, including "at approximately 2:36 p.m." on May 15, 2026.
    11. present: Several precise times are given, such as "approximately 2:36 p.m." and "6:12 p.m."
    12. present: Gives precise times: "approximately 2:36 p.m.", "3:30 p.m.", and "6:12 p.m.".
    13. present: Precise times are given, including 'approximately 2:36 p.m.' and 'approximately 6:12 p.m.'.
    14. present: Timestamps the sequence: "at approximately 2:36 p.m.", "At approximately 3:30 p.m.", "6:12 p.m.".
    15. present: Timestamps the sequence, "at approximately 2:36 p.m." and "At approximately 3:30 p.m."
    16. present: Precise times are given, including "approximately 2:36 p.m." and "approximately 6:12 p.m.".
    17. present: Precise times are given, including "at approximately 2:36 p.m." and "approximately 6:12 p.m."
    18. present: Times are precise: "May 15, 2026, at approximately 2:36 p.m." and 3:30 p.m.
    19. present: Several clock times are given, including "approximately 2:36 p.m." on May 15, 2026.
    20. present: Uses precise clock times such as "approximately 2:36 p.m." and "approximately 6:12 p.m." on a stated date.
    21. present: Several precise times are given, including "at approximately 2:36 p.m." on May 15, 2026.
    22. present: Precise times are given, such as "approximately 2:36 p.m." on May 15, 2026.
    23. present: Precise times are given, including "at approximately 2:36 p.m." and "At approximately 6:12 p.m."
    24. present: Uses precise clock times, "at approximately 2:36 p.m." and "At approximately 6:12 p.m."
    25. present: Precise times are given, such as "approximately 2:36 p.m." and "approximately 6:12 p.m." on May 15, 2026.
  • Impactabsent0/25

    Final assessment

    Absent, 0 of 25: no injuries, damage or ongoing danger are stated; the note reports "one person was in custody and one weapon was recovered".

    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: No injury, danger, or severity is stated; the note reports a suspect in custody and a weapon recovered.
    2. absent: Reports a person in custody and a weapon recovered but no statement of danger or harm caused.
    3. absent: No injuries, danger or severity are asserted; a suspect is reported in custody instead.
    4. absent: It reports a person in custody and a weapon recovered but states no injury, danger, or severity.
    5. absent: It reports a suspect in custody and a weapon recovered without stating any harm or danger.
    6. absent: No harm or severity is described; instead it notes a suspect in custody and a weapon recovered.
    7. absent: No injuries, danger, or severity are stated; the suspect is already in custody.
    8. absent: No injuries or dangers to the community are stated; the suspect is already in custody.
    9. absent: With one person in custody and a weapon recovered, no potential harm to readers is stated.
    10. absent: It reports a person in custody and a weapon recovered, but never states potential harm or severity.
    11. absent: No injuries or damage are described, and the account closes with a suspect in custody.
    12. absent: It reports a person in custody and a weapon recovered without stating any danger or harm.
    13. absent: No injuries or danger level are stated, only that a suspect and weapon were recovered.
    14. absent: No harm or severity is described; it reports a suspect in custody and a weapon recovered.
    15. absent: No injuries or potential consequences are described; a suspect is in custody and a weapon recovered.
    16. absent: No injury, danger or severity is stated; the suspect is already in custody.
    17. absent: It reports a person in custody and a weapon recovered but states no injury or danger level.
    18. absent: It reports a custody arrest and recovered weapon without stating danger or potential harm.
    19. absent: No injuries, danger level, or potential harm to the community is stated.
    20. absent: Notes an arrest and a recovered weapon but never states danger, injury, or severity to the community.
    21. absent: It reports a suspect in custody and a weapon recovered but never states harm or danger to the community.
    22. absent: No injuries or dangers are described; the narrative ends with a suspect in custody and a weapon recovered.
    23. absent: It reports a person in custody and a weapon recovered but never states harm or danger to people.
    24. absent: No injuries, danger level, or potential consequence is stated; a suspect is already in custody.
    25. absent: It reports a suspect in custody and a weapon recovered, but never states danger or possible harm to readers.

Coded by Claude Opus 5

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

About this analysis
Context

Background

University of Maryland Police Department community notices published via UMPD News.
Analysis

Key Findings

Official UMPD News page preserves complete community notice email text.
Outcome
See official notice for investigation status.
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 Maryland, College Park: Follow-Up In Off-Campus Incident." Incident of May 15, 2026. Added July 2026. https://campusalertarchive.com/case/university-of-maryland-follow-campus-incident-2026-05-15/

Download case JSON

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

Tags
marylandumdcommunity-noticeactive-threatUnder Investigation
Added July 2026Updated July 2026Via ingestion