Wednesday, July 24, 2013

Pensacola Airport Will Not Be Homeland Security Compliant Under Hayward Plan

Airport Director Donovan asked Council to allow the airport to downsize its fire/rescue protection to the "minimum required by the FAA for an airport our size". Minimum required?  Really?

The issue arises that by doing this the airport will not be in compliance with the NIMS (National Incident Management System) according to the Fire Union letter at the link below.

ARFF-Staffing

On February 28, 2003, the President issued Homeland Security Presidential Directive 5 (HSPD–5), “Management of Domestic Incidents,” which directed the Secretary of Homeland Security to develop and administer a National Incident Management System (NIMS). This system provides a consistent nationwide template to enable federal, state, tribal and local governments, nongovernmental organizations (NGOs) and the private sector to work together to prevent, protect against, respond to, recover from and mitigate the effects of incidents, regardless of cause, size, location or complexity. This consistency provides the foundation for utilization of NIMS for all incidents, ranging from daily occurrences to incidents requiring a coordinated federal response.


HSPD–5 requires all federal departments and agencies to adopt NIMS and to use it in their individual incident management programs and activities, as well as in support of all actions taken to assist state, tribal and local governments. The directive requires federal departments and agencies to make adoption of NIMS by state, tribal and local organizations a condition for federal preparedness assistance (through grants, contracts and other activities). NIMS recognizes the role that NGOs and the private sector have in preparedness and activities to prevent, protect against, respond to, recover from and mitigate the effects of incidents.

So will the City adopting the "minimum required" really be penny wise and pound foolish if we are trying to GROW our airport?
http://www.fema.gov/implementation-and-compliance-guidance-stakeholders




No comments: