Skip to content
Campus Alert Archive
IU Indy

Armed subject near Engineering Science and Gateway Garage then custody

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

IU Public Safety warned of a dangerous situation near Engineering Science & Technology, reported an armed male inside Gateway Garage with police in pursuit, then updated that IMPD detained the unaffiliated suspect.

Alerts
3
Response
Killed
Injured
Institution
Indiana University Indianapolis
Public R1 · IN
All IU Indy cases →
~30,000 studentsIU Notify / @IUpolice
Documented Timeline

Alert Sequence

3 messages in sequence · 3 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 verbatim136 chars
IU Indy emergency: A dangerous situation is occurring near Engineering Science & Technology . Avoid the area. Call 911 with information.
Dual independent X fetch match 2026-08-02. SPN 523.
UPDATETwitter/X+13 min
Verified verbatim135 chars
IU Indy emergency: An armed male is reported inside Gateway Garage. Metropolitan police and IUPD Police are in pursuit. Avoid the area.
Dual independent X fetch match 2026-08-02. SPN 523.
ALL CLEARTwitter/X+2h 14m
Verified verbatim230 chars
UPDATE: On February 14, 2026, the IU Police Department assisted the Indianapolis Metropolitan Police Department with an alleged armed subject unaffiliated with IU in the area of Gateway Garage. IMPD was able to detain the suspect.
Dual independent X fetch match 2026-08-02. SPN 523.
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.

IU Indy emergency: A dangerous situation is occurring near Engineering Science & Technology . Avoid the area. Call 911 with information.

  • Sourceabsent0/25

    Final assessment

    Majority 25/25 absent. No campus brand, agency name, or alert signature appears in the text.

    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 campus brand, agency name, or alert signature appears in the text.
    2. absent: The wording never says who is sending the notice.
    3. absent: Source is absent: no university, police, or alert-system label is stated.
    4. absent: Nothing identifies an issuing authority or branded channel.
    5. absent: No sender tag or institutional self-naming is present.
    6. absent: Recipients cannot tell the source from the body alone.
    7. absent: Source codes zero because authority language is missing.
    8. absent: There is no ALERT brand or school name to credit as source.
    9. absent: The message jumps to content without naming who issued it.
    10. absent: No public-safety or campus office is identified as sender.
    11. absent: Source fails: blank on branded signature and agency.
    12. absent: Issuing body is not stated in any form.
    13. absent: Without a signature or school name, source is absent.
    14. absent: The text omits sender identification entirely.
    15. absent: No authority cue meets the source element rule.
    16. absent: Source not present under the branding or agency tests.
    17. absent: Who authored the alert is left unspecified.
    18. absent: There is no institutional label to treat as source.
    19. absent: Sender identity cannot be read from the message.
    20. absent: Source scores absent on this wording.
    21. absent: No alert header or campus self-reference is included.
    22. absent: The body never attributes the notice to an issuer.
    23. absent: Authority line is missing from start to end.
    24. absent: Source element fails for lack of named sender.
    25. absent: Nothing in the text names a sending organization.
  • Hazardpresent25/25

    Final assessment

    Majority 25/25 present. Hazard is specific: the text names "IU Indy emergency: A dangerous situatio…".

    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 specific: the text names "IU Indy emergency: A dangerous situatio…".
    2. present: A concrete threat appears as "IU Indy emergency: A dangerous situatio…".
    3. present: The what of the emergency is "IU Indy emergency: A dangerous situatio…", not a vague incident label.
    4. present: "IU Indy emergency: A dangerous situatio…" satisfies hazard by naming the condition or threat.
    5. present: Readers learn the hazard type from "IU Indy emergency: A dangerous situatio…".
    6. present: Hazard present via the explicit phrase "IU Indy emergency: A dangerous situatio…".
    7. present: The threat is particularized as "IU Indy emergency: A dangerous situatio…".
    8. present: Coding H=1 because "IU Indy emergency: A dangerous situatio…" is a named hazard.
    9. present: Specific danger language: "IU Indy emergency: A dangerous situatio…".
    10. present: The alert states the problem as "IU Indy emergency: A dangerous situatio…".
    11. present: Hazard element met by "IU Indy emergency: A dangerous situatio…".
    12. present: "IU Indy emergency: A dangerous situatio…" is more than a generic emergency word.
    13. present: Threat identity is clear from "IU Indy emergency: A dangerous situatio…".
    14. present: The message pins the hazard to "IU Indy emergency: A dangerous situatio…".
    15. present: Named condition "IU Indy emergency: A dangerous situatio…" counts as hazard.
    16. present: H is present: "IU Indy emergency: A dangerous situatio…" tells what is wrong.
    17. present: Concrete hazard wording includes "IU Indy emergency: A dangerous situatio…".
    18. present: The incident type is given as "IU Indy emergency: A dangerous situatio…".
    19. present: "IU Indy emergency: A dangerous situatio…" is the stated threat or weather/system hazard.
    20. present: Hazard codes yes on "IU Indy emergency: A dangerous situatio…".
    21. present: Specifics beat generics here: "IU Indy emergency: A dangerous situatio…".
    22. present: The text's hazard signal is "IU Indy emergency: A dangerous situatio…".
    23. present: What happened is labeled "IU Indy emergency: A dangerous situatio…".
    24. present: Hazard present with the phrase "IU Indy emergency: A dangerous situatio…".
    25. present: Threat naming succeeds through "IU Indy emergency: A dangerous situatio…".
  • Locationpresent25/25

    Final assessment

    Majority 25/25 present. Location is given through "IU Indy emergency: A dangerous situatio…".

    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 given through "IU Indy emergency: A dangerous situatio…".
    2. present: Place is specified as "IU Indy emergency: A dangerous situatio…".
    3. present: Where is answered by "IU Indy emergency: A dangerous situatio…".
    4. present: "IU Indy emergency: A dangerous situatio…" functions as the location element.
    5. present: The alert situates the event with "IU Indy emergency: A dangerous situatio…".
    6. present: Geographic or campus place: "IU Indy emergency: A dangerous situatio…".
    7. present: L=1 because "IU Indy emergency: A dangerous situatio…" names where this applies.
    8. present: Recipients are told the place via "IU Indy emergency: A dangerous situatio…".
    9. present: Location present in the phrase "IU Indy emergency: A dangerous situatio…".
    10. present: A campus or building reference "IU Indy emergency: A dangerous situatio…" covers location.
    11. present: The where cue is "IU Indy emergency: A dangerous situatio…".
    12. present: "IU Indy emergency: A dangerous situatio…" identifies the affected area.
    13. present: Place naming succeeds with "IU Indy emergency: A dangerous situatio…".
    14. present: Location codes yes on "IU Indy emergency: A dangerous situatio…".
    15. present: Site detail appears as "IU Indy emergency: A dangerous situatio…".
    16. present: The message anchors place with "IU Indy emergency: A dangerous situatio…".
    17. present: "IU Indy emergency: A dangerous situatio…" is enough location under the rubric.
    18. present: Affected place language: "IU Indy emergency: A dangerous situatio…".
    19. present: L is present via "IU Indy emergency: A dangerous situatio…".
    20. present: Campus geography is marked by "IU Indy emergency: A dangerous situatio…".
    21. present: Where this matters is "IU Indy emergency: A dangerous situatio…".
    22. present: The text localizes to "IU Indy emergency: A dangerous situatio…".
    23. present: Location element met by "IU Indy emergency: A dangerous situatio…".
    24. present: Place is not left blank: "IU Indy emergency: A dangerous situatio…".
    25. present: Spatial reference "IU Indy emergency: A dangerous situatio…" supports L=1.
  • Guidancepresent25/25

    Final assessment

    Majority 25/25 present. Guidance is the instruction "Avoid the area".

    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 the instruction "Avoid the area".
    2. present: Protective action appears as "Avoid the area".
    3. present: Recipients are told to act via "Avoid the area".
    4. present: "Avoid the area" is a direct what-to-do line.
    5. present: G=1 because "Avoid the area" instructs the audience.
    6. present: The alert directs action with "Avoid the area".
    7. present: Guidance present: "Avoid the area".
    8. present: A clear instruction is "Avoid the area".
    9. present: What to do is stated as "Avoid the area".
    10. present: "Avoid the area" counts as protective guidance.
    11. present: Action language "Avoid the area" meets guidance.
    12. present: The message tells people "Avoid the area".
    13. present: Guidance codes yes on "Avoid the area".
    14. present: Operational direction: "Avoid the area".
    15. present: Instructional content includes "Avoid the area".
    16. present: "Avoid the area" is audience-facing guidance.
    17. present: G is present via the cue "Avoid the area".
    18. present: Protective or operational order "Avoid the area" is explicit.
    19. present: The text's guidance signal is "Avoid the area".
    20. present: Recipients receive the directive "Avoid the area".
    21. present: What-to-do element satisfied by "Avoid the area".
    22. present: "Avoid the area" tells the public how to respond or operate.
    23. present: Guidance met through "Avoid the area".
    24. present: Action instruction present: "Avoid the area".
    25. present: The alert's order to the audience is "Avoid the area".
  • Timeabsent0/25

    Final assessment

    Majority 25/25 absent. No clock time, date, or recency word such as now or today 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, date, or recency word such as now or today appears.
    2. absent: Time is absent from the alert text.
    3. absent: Nothing tells recipients when this applies.
    4. absent: T=0 because temporal cues are missing.
    5. absent: No day, hour, or immediate language is stated.
    6. absent: The message omits timing entirely.
    7. absent: Time element fails on this wording.
    8. absent: When is left unspecified.
    9. absent: No calendar or clock reference is present.
    10. absent: Temporal information cannot be found.
    11. absent: Without a time cue, T is zero.
    12. absent: The alert is silent on schedule.
    13. absent: Time codes absent here.
    14. absent: Recency language is missing.
    15. absent: T fails the when test.
    16. absent: No today/now/clock marker appears.
    17. absent: Timing is not established by the text.
    18. absent: Date and hour are both omitted.
    19. absent: Temporal element is not satisfied.
    20. absent: The body lacks any when cue.
    21. absent: Time not present under the rubric.
    22. absent: Schedule detail is blank.
    23. absent: No temporal anchor is given.
    24. absent: T is absent on timeless wording.
    25. absent: When-information is not included.
  • Impactpresent25/25

    Final assessment

    Majority 25/25 present. Impact is conveyed by "dangerous".

    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. present: Impact is conveyed by "dangerous".
    2. present: Consequence language appears as "dangerous".
    3. present: Severity or harm is signaled by "dangerous".
    4. present: "dangerous" states what the hazard does to people or operations.
    5. present: I=1 because "dangerous" implies real-world impact.
    6. present: The alert spells impact through "dangerous".
    7. present: Impact present: "dangerous".
    8. present: Operational or safety consequence "dangerous" is explicit.
    9. present: What could happen is framed as "dangerous".
    10. present: "dangerous" counts as impact beyond bare hazard naming.
    11. present: Impact element met by "dangerous".
    12. present: Severity cue "dangerous" supports I=1.
    13. present: I codes yes on "dangerous".
    14. present: The text links hazard to effect via "dangerous".
    15. present: Consequence wording: "dangerous".
    16. present: "dangerous" shows stakes for the campus community.
    17. present: Impact is not left implicit only: "dangerous".
    18. present: Harm or closure effect appears as "dangerous".
    19. present: I is present via "dangerous".
    20. present: The message states impact with "dangerous".
    21. present: Real-world effect language "dangerous" is included.
    22. present: Impact signal: "dangerous".
    23. present: "dangerous" communicates severity or disruption.
    24. present: Consequence is clear from "dangerous".
    25. present: Impact present through the phrase "dangerous".

Coded by SuperGrok Heavy 4.5

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

About this analysis
Context

Background

IU Public Safety posts multi-campus IU Notify alerts on @IUpolice.
Analysis

Key Findings

Avoid-area dangerous situation escalating to armed subject in Gateway Garage; IMPD custody.
Outcome
Suspect detained by IMPD; no ongoing threat.
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
Cite this case

Campus Alert Archive. "Indiana University Indianapolis: Armed subject near Engineering Science and Gateway Garage then custody." Incident of February 14, 2026. Added August 2026. https://campusalertarchive.com/case/indiana-university-indianapolis-gateway-garage-armed-subject-2026-02-14/

Download case JSON

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

Tags
public-r1indianaarmed-personiu-indy
Added August 2026Updated August 2026Via ingestion