Information CrimeRadar provides is made available solely to protect the public. Using this information to harass, threaten, or harm anyone is prohibited. Information is provided by third parties and may have errors. We cannot guarantee the accuracy, completeness, or timeliness of the information. Location data may not be 100% accurate. Use extreme care and always verify information through official sources and exercise caution and judgment when using CrimeRadar. By clicking continue, I agree I have read and understand the above and agree to these terms and conditions.
Emergency Response to Hemorrhage Near Prospect Avenue, Kansas City MO
Medical Emergency
Near Prospect Ave, Kansas City, MO 64124
Emergency responders were sent to assist with a bleeding issue near Prospect Avenue.
Audio|Source: Kansas City Fire
00:27
Transcript: Medic 34. 30% prospect on a hemorrhage, A4[1]. Middick 34. 30 version prospect, Hemorrhage, A4. Cars of the package, if you want to go up, you can double park. Medicin 19 and servicing quarters.
Police codes explained
The following codes appeared in the transcript and are explained below:
[1]
A4: EMS radio channel code for this incident
Disclaimer: This was transcribed by AI and may contain errors. Please verify the information independently.
Location mentioned:
Near Prospect Ave, Kansas City, MO 64124
Correct
Incorrect
Explore More on Kansas City, MO Crime Map
Recent Medical Emergency Incidents in Kansas City, MO
Traffic accident, 83, car 104, 104, Pumper 10, truck 3, 856, I-70, and prospect on a traffic accident, 84[1].
Pover 14 responding. Pover 14 responding. Pumper 14 responding. Pumper 10, Medics 551, near Lexington Ave, sick person 83. Pover 10, Medics 551, near Lexington Ave, sick person A3.
Responding, near Prospect Ave, Pady Manor, 79-year-old female, possibly low on blood, altered mental status, patient transport 1921.
Company 3 and Engine 3 are on scene and running command near Olive Street. Commit 13 is mentioned. (name withheld) says Engine 3 is running command and gives time 10:44. The location is a known problem and seems not secure.