1. PIA Format The PIA is a review of Operations. It is used to analyze: What was done? What was done right? What could have been done better?

2. Tech Rescue Incident “Unconscious person on a 54’ boat” 1029 hrs 2/22/11 614 Front St. Type-Med

3. Alarm Was the alarm reported, received, and transmitted correctly? Entered: 10:29:31 Dispatched: 10:29:37

4. Dispatch Medic 23 Engine 6 (Engine 25)

5. Balanced Type to Tech Rescue Engine 24 Engine 16 (TR 16) Medic 12 Chief 25 MSO 15 Battalion 21 Ladder 11

6. Initial Actions and Size-Up

7. Ivar’s Command • Command Timeline • E25 and M23 On-Scene 1040 • Established by E25 1045 • Safety 1100 • Rescue Group 1107 • Termination 1128 • M23 Transporting 1131 • M23 @ Harborview 1158

9. Incident Action Plan Access and stabilize patient Transfer patient to M23 Transport within “Golden Hour”

10. Incident Action Plan

11. Incident Action Plan

12. Incident Action Plan

13. Incident Action Plan

14. Incident Action Plan

15. Incident Action Plan

16. Incident Action Plan

17. Incident Action Plan

18. Incident Action Plan

19. Incident Action Plan

20. Incident Action Plan

21. TRAFFIC CONTROL: Did law enforcement assist in traffic control? Did you open the street as soon as possible?

22. TRAFFIC CONTROL:

23. COMMUNICATIONS: Were radio communications clear and concise? Was the NFA Communication Model followed to include the “Final Handshake?”

24. PUBLIC RELATIONS: Did the actions or performance of the fire department enhance public relations?

25. Questionnaire Comments “Priority was getting all on-scene personnel to wear Personal Flotation Devices when working over water conditions.” WAC 296-800-16070 -Make sure your employees are protected from drowning. You must:(1) Provide and make sure your employees wear personal flotation devices (PFD).• When they work in areas where the danger of drowning exists, such as:     – On the water.     – Over the water.    – Alongside the water. Note: Employees are not exposed to the danger of drowning when: Employees are working behind standard height and strength guardrails. Employees are working inside operating cabs or stations that eliminate the possibility of accidentally falling into the water. Employees are wearing an approved safety belt with a lifeline attached that prevents the possibility of accidentally falling into the water.

26. Questionnaire Comments “Conditions were wet and icy.” “This was an experimental craft and the hatches opened from the center outward making extrication difficult.” “Get a representative from the Ferry system early on in the incident to the command post.” “Rescue group supervisor to update IC on a regular basis.” “ Do not place apparatus on the ferry ramp.” “ Communications error with Command. Incoming units didn’t know my (Rescue) role.” “ … at some point the plan changed.”

27. Questionnaire Comments “I believe it would have been safer to have the skiff come closer to shore for patient removal rather than the ferry dock.” “I don’t remember Safety being established.” “Get a representative from the Ferry system early on in the incident to the command post.” “ Crews and patient not tied off on ferry ramp or the skiff.”

28. Lessons Learned • Communicate plans and change of plans clearly • Very good use of PFDs • Tech Rescue 16 is a stand alone unit now • 1st Alarm- TR16 and crew • 2nd Alarm- TR16 and on-duty Technicians in that Zone • 3rd Alarm- TR16 and on-duty Technicians in all Zones • Good patient care and outcome of call for extremely unique circumstances • (snowing, experimental boat with unique features, limited access, etc.)

29. Lessons Learned • Tag lines for personnel and patient could be considered for additional safety • Mukilteo ferry ramp is not structurally very stable but can lower to meet most boats • Consider all access points when receiving patients off of boats • (i.e. boat launch, Silver Cloud beach, etc.) • Face to face communications are still very valuable in clearing up any confusion on scene • Radio Tactical Channels should be used for Technical Rescue when necessary