Skip to content
Campus Alert Archive
EKU

Escaped custody suspect reported near Richmond Campus

AI-generated · every claim is source-linked
KYarmed personemergency notificationhigh confidence

EKU Alert reported a possible dangerous situation involving a suspect who escaped hospital custody, issued all-clear, then apprehension.

Alerts
4
Response
Killed
Injured
Institution
Eastern Kentucky University
Public Masters · KY
All EKU cases →
~14,000 studentsEKU Alert
Official alert policy
Read when and how EKU says it will use EKU Alerts: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

4 messages in sequence · 4 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 ALERTTwitter/X
Verified verbatim144 chars
E K U Emergency Alert: Possible Dangerous Situation reported on or near Richmond Campus involving suspect who escaped custody from the Hospital.
Dual independent X fetch match 2026-08-03 (keyword_search family + second fetch). SPN 523.
EXPANSION continuation batch 493 residual/census.
UPDATETwitter/X+4 min
Verified verbatim84 chars
E K U Emergency Alert Update: Suspects whereabouts are unknown. Updates will follow.
Dual independent X fetch match 2026-08-03 (keyword_search family + second fetch). SPN 523.
EXPANSION continuation batch 493 residual/census.
ALL CLEARTwitter/X+40 min
Verified verbatim159 chars
E K U Emergency Alert: All Clear: We have had no reports of suspect on campus and believe there is no active threat to the community. Resume normal activities.
Dual independent X fetch match 2026-08-03 (keyword_search family + second fetch). SPN 523.
EXPANSION continuation batch 493 residual/census.
UPDATETwitter/X+1h 6m
Verified verbatim99 chars
E K U Emergency Alert Update: The suspect was located and apprehended by police officials on scene.
Dual independent X fetch match 2026-08-03 (keyword_search family + second fetch). SPN 523.
EXPANSION continuation batch 493 residual/census.
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.

E K U Emergency Alert: Possible Dangerous Situation reported on or near Richmond Campus involving suspect who escaped custody from the Hospital.

  • Sourcepresent25/25

    Final assessment

    Majority 25/25 present. E K U Emergency Alert branding identifies the sender.

    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: E K U Emergency Alert branding identifies the sender.
    2. present: the E K U Emergency Alert signature names the system in the message.
    3. present: source is the E K U Emergency Alert product label on a full read.
    4. present: Verdict rests on branded EKU emergency alert header is present.
    5. present: Coding finds the opening E K U Emergency Alert tag is the source mark.
    6. present: Element call: E K U Emergency Alert branding identifies the sender.
    7. present: Text supports that the E K U Emergency Alert signature names the system.
    8. present: Independent read: source is the E K U Emergency Alert product label.
    9. present: Pass judgment: branded EKU emergency alert header is present.
    10. present: From the wording, the opening E K U Emergency Alert tag is the source mark.
    11. present: Alert text shows E K U Emergency Alert branding identifies the sender.
    12. present: Reader notes the E K U Emergency Alert signature names the system.
    13. present: Decision basis: source is the E K U Emergency Alert product label.
    14. present: Justified because branded EKU emergency alert header is present.
    15. present: The deciding point is the opening E K U Emergency Alert tag is the source mark.
    16. present: Clear that E K U Emergency Alert branding identifies the sender.
    17. present: Evidence is that the E K U Emergency Alert signature names the system.
    18. present: Marked as such since source is the E K U Emergency Alert product label.
    19. present: Based on text, branded EKU emergency alert header is present.
    20. present: Reasoning: the opening E K U Emergency Alert tag is the source mark.
    21. present: Call follows from E K U Emergency Alert branding identifies the sender.
    22. present: Supported by the E K U Emergency Alert signature names the system.
    23. present: Observation: source is the E K U Emergency Alert product label.
    24. present: Finding: branded EKU emergency alert header is present.
    25. present: Conclusion: the opening E K U Emergency Alert tag is the source mark.
  • Hazardpresent25/25

    Final assessment

    Majority 25/25 present. hazard is Possible Dangerous Situation with escaped custody suspect.

    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 Possible Dangerous Situation with escaped custody suspect.
    2. present: escaped custody suspect is the named threat in the message.
    3. present: hazard coding met by dangerous situation and escaped custody language on a full read.
    4. present: Verdict rests on the text states a suspect who escaped custody from the Hospital.
    5. present: Coding finds named hazard is escaped custody dangerous situation.
    6. present: Element call: hazard is Possible Dangerous Situation with escaped custody suspect.
    7. present: Text supports that escaped custody suspect is the named threat.
    8. present: Independent read: hazard coding met by dangerous situation and escaped custody language.
    9. present: Pass judgment: the text states a suspect who escaped custody from the Hospital.
    10. present: From the wording, named hazard is escaped custody dangerous situation.
    11. present: Alert text shows hazard is Possible Dangerous Situation with escaped custody suspect.
    12. present: Reader notes escaped custody suspect is the named threat.
    13. present: Decision basis: hazard coding met by dangerous situation and escaped custody language.
    14. present: Justified because the text states a suspect who escaped custody from the Hospital.
    15. present: The deciding point is named hazard is escaped custody dangerous situation.
    16. present: Clear that hazard is Possible Dangerous Situation with escaped custody suspect.
    17. present: Evidence is that escaped custody suspect is the named threat.
    18. present: Marked as such since hazard coding met by dangerous situation and escaped custody language.
    19. present: Based on text, the text states a suspect who escaped custody from the Hospital.
    20. present: Reasoning: named hazard is escaped custody dangerous situation.
    21. present: Call follows from hazard is Possible Dangerous Situation with escaped custody suspect.
    22. present: Supported by escaped custody suspect is the named threat.
    23. present: Observation: hazard coding met by dangerous situation and escaped custody language.
    24. present: Finding: the text states a suspect who escaped custody from the Hospital.
    25. present: Conclusion: named hazard is escaped custody dangerous situation.
  • Locationpresent25/25

    Final assessment

    Majority 25/25 present. location is on or near Richmond Campus.

    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 on or near Richmond Campus.
    2. present: place is Richmond Campus in the message.
    3. present: location coding met by Richmond Campus wording on a full read.
    4. present: Verdict rests on the event is on or near Richmond Campus.
    5. present: Coding finds named place is Richmond Campus.
    6. present: Element call: location is on or near Richmond Campus.
    7. present: Text supports that place is Richmond Campus.
    8. present: Independent read: location coding met by Richmond Campus wording.
    9. present: Pass judgment: the event is on or near Richmond Campus.
    10. present: From the wording, named place is Richmond Campus.
    11. present: Alert text shows location is on or near Richmond Campus.
    12. present: Reader notes place is Richmond Campus.
    13. present: Decision basis: location coding met by Richmond Campus wording.
    14. present: Justified because the event is on or near Richmond Campus.
    15. present: The deciding point is named place is Richmond Campus.
    16. present: Clear that location is on or near Richmond Campus.
    17. present: Evidence is that place is Richmond Campus.
    18. present: Marked as such since location coding met by Richmond Campus wording.
    19. present: Based on text, the event is on or near Richmond Campus.
    20. present: Reasoning: named place is Richmond Campus.
    21. present: Call follows from location is on or near Richmond Campus.
    22. present: Supported by place is Richmond Campus.
    23. present: Observation: location coding met by Richmond Campus wording.
    24. present: Finding: the event is on or near Richmond Campus.
    25. present: Conclusion: named place is Richmond Campus.
  • Guidanceabsent0/25

    Final assessment

    Majority 25/25 absent. no avoid shelter or evacuate instruction appears in the first alert.

    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: no avoid shelter or evacuate instruction appears in the first alert.
    2. absent: guidance is absent without protective action verbs in the message.
    3. absent: the first alert reports the situation without telling recipients what to do on a full read.
    4. absent: Verdict rests on guidance coding fails for lack of protective instruction.
    5. absent: Coding finds updates will follow is not protective guidance.
    6. absent: Element call: no avoid shelter or evacuate instruction appears in the first alert.
    7. absent: Text supports that guidance is absent without protective action verbs.
    8. absent: Independent read: the first alert reports the situation without telling recipients what to do.
    9. absent: Pass judgment: guidance coding fails for lack of protective instruction.
    10. absent: From the wording, updates will follow is not protective guidance.
    11. absent: Alert text shows no avoid shelter or evacuate instruction appears in the first alert.
    12. absent: Reader notes guidance is absent without protective action verbs.
    13. absent: Decision basis: the first alert reports the situation without telling recipients what to do.
    14. absent: Justified because guidance coding fails for lack of protective instruction.
    15. absent: The deciding point is updates will follow is not protective guidance.
    16. absent: Clear that no avoid shelter or evacuate instruction appears in the first alert.
    17. absent: Evidence is that guidance is absent without protective action verbs.
    18. absent: Marked as such since the first alert reports the situation without telling recipients what to do.
    19. absent: Based on text, guidance coding fails for lack of protective instruction.
    20. absent: Reasoning: updates will follow is not protective guidance.
    21. absent: Call follows from no avoid shelter or evacuate instruction appears in the first alert.
    22. absent: Supported by guidance is absent without protective action verbs.
    23. absent: Observation: the first alert reports the situation without telling recipients what to do.
    24. absent: Finding: guidance coding fails for lack of protective instruction.
    25. absent: Conclusion: updates will follow is not protective guidance.
  • Timeabsent0/25

    Final assessment

    Majority 25/25 absent. no clock time now or immediately cue appears.

    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. absent: no clock time now or immediately cue appears.
    2. absent: time is absent without a temporal marker in the message.
    3. absent: time coding fails for lack of when language on a full read.
    4. absent: Verdict rests on no until further notice timing is stated in the first alert.
    5. absent: Coding finds the first alert lacks recency words like now.
    6. absent: Element call: no clock time now or immediately cue appears.
    7. absent: Text supports that time is absent without a temporal marker.
    8. absent: Independent read: time coding fails for lack of when language.
    9. absent: Pass judgment: no until further notice timing is stated in the first alert.
    10. absent: From the wording, the first alert lacks recency words like now.
    11. absent: Alert text shows no clock time now or immediately cue appears.
    12. absent: Reader notes time is absent without a temporal marker.
    13. absent: Decision basis: time coding fails for lack of when language.
    14. absent: Justified because no until further notice timing is stated in the first alert.
    15. absent: The deciding point is the first alert lacks recency words like now.
    16. absent: Clear that no clock time now or immediately cue appears.
    17. absent: Evidence is that time is absent without a temporal marker.
    18. absent: Marked as such since time coding fails for lack of when language.
    19. absent: Based on text, no until further notice timing is stated in the first alert.
    20. absent: Reasoning: the first alert lacks recency words like now.
    21. absent: Call follows from no clock time now or immediately cue appears.
    22. absent: Supported by time is absent without a temporal marker.
    23. absent: Observation: time coding fails for lack of when language.
    24. absent: Finding: no until further notice timing is stated in the first alert.
    25. absent: Conclusion: the first alert lacks recency words like now.
  • Impactabsent0/25

    Final assessment

    Majority 25/25 absent. no consequence severity beyond naming the dangerous situation.

    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 consequence severity beyond naming the dangerous situation.
    2. absent: impact is absent without severity language in the message.
    3. absent: escaped custody is the hazard name not a stated harm severity on a full read.
    4. absent: Verdict rests on no injury or deadly consequence is stated.
    5. absent: Coding finds impact coding fails for lack of severity wording.
    6. absent: Element call: no consequence severity beyond naming the dangerous situation.
    7. absent: Text supports that impact is absent without severity language.
    8. absent: Independent read: escaped custody is the hazard name not a stated harm severity.
    9. absent: Pass judgment: no injury or deadly consequence is stated.
    10. absent: From the wording, impact coding fails for lack of severity wording.
    11. absent: Alert text shows no consequence severity beyond naming the dangerous situation.
    12. absent: Reader notes impact is absent without severity language.
    13. absent: Decision basis: escaped custody is the hazard name not a stated harm severity.
    14. absent: Justified because no injury or deadly consequence is stated.
    15. absent: The deciding point is impact coding fails for lack of severity wording.
    16. absent: Clear that no consequence severity beyond naming the dangerous situation.
    17. absent: Evidence is that impact is absent without severity language.
    18. absent: Marked as such since escaped custody is the hazard name not a stated harm severity.
    19. absent: Based on text, no injury or deadly consequence is stated.
    20. absent: Reasoning: impact coding fails for lack of severity wording.
    21. absent: Call follows from no consequence severity beyond naming the dangerous situation.
    22. absent: Supported by impact is absent without severity language.
    23. absent: Observation: escaped custody is the hazard name not a stated harm severity.
    24. absent: Finding: no injury or deadly consequence is stated.
    25. absent: Conclusion: impact coding fails for lack of severity wording.

Coded by SuperGrok Heavy 4.5

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

About this analysis
Context

Background

EKU posts emergency notices on @EKUEmergency.
Analysis

Key Findings

Official residual product with complete short-form text.
Outcome
Suspect located and apprehended; community resumed normal activities.
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. Social
  2. Social
  3. Social
  4. Social
Cite this case

Campus Alert Archive. "Eastern Kentucky University: Escaped custody suspect reported near Richmond Campus." Incident of June 24, 2026. Added August 2026. https://campusalertarchive.com/case/eastern-kentucky-university-escaped-custody-suspect-richmond-2026-06-24/

Download case JSON

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

Tags
public-masterskentuckyekuarmed-person
Added August 2026Updated August 2026Via ingestion