План IRAP по подготовке к землетрясениям в аэропорту Стамбула (İGA)

Recommendation: Implement the IRAP Plan for Earthquake Preparedness at Istanbul Airport (İGA) immediately, using a 12-month roadmap to safeguard critical operations. The plan defines amaçlarla and uses ifade-driven targets, kullanılarak sitemizdeki dashboards, and a goal-oriented approach to keep airfield and terminal functions performing during a strong earthquake. Near-term yatırım will be prioritized, and bağlı to rapid risk reduction through yöntemleriyle.

Governance and coordination: The risk management team of İGA leads day-to-day execution, and the bakanı tarafından provides policy backing and oversight. The IRAP framework integrates environmental yöntemler and links hazard controls to terminal and airfield operations. Close coordination with authorities and airport tenants ensures timely information sharing during incidents and keeps the plan aligned with communities’ needs at the sitesinin level.

Concrete actions and metrics: We will complete hazard assessments and geotechnical surveys within the first 90 days, then implement prioritized retrofits for critical structures within 18 months. The electrical and communications backbone will feature redundant power feeders and seismic-hardening, aiming for 99.9% uptime in simulated earthquakes. Emergency response times for field crews will be under 5 minutes during drills, and staff will conduct quarterly field exercises plus monthly tabletop sessions. An on-site cache powering 72 hours of essential supplies and communications hardware ensures continuity when external logistics are disrupted.

Investment and environmental alignment: This plan emphasizes near-term yatırım in retrofits, backup power, and secure communications, while integrating environmental yöntemler to minimize ecological impact. Key actions include seismic upgrades for hangars, improved drainage on aprons and runways, and water-supply resilience for emergency operations. The investment approach remains bağlı to risk-based prioritization and is tracked through sitemizdeki analytics to monitor progress toward the goal. It also reflects soylu civic responsibilities within the communities around sitesinin.

Operational continuity, accountability, and monitoring: We will engage with nearby municipalities to align evacuation routes and crowd management. Training covers air traffic control, firefighting, and medical teams. The sitesinin operational readiness improves as drills test coordination with rescue teams and ensure secure communications during power outages. KPIs update monthly, and the plan is reviewed tarafından the ministry and İGA leadership every quarter, with updates published on the sitemizdeki portal to maintain transparency and accountability for passengers and staff.

Define IRAP Governance, Roles, and Accountability within Istanbul Airport Operations

Establish a formal IRAP Governance Board within Istanbul Airport Operations and appoint an IRAP Lead to own the yürütülüğünü of the plan. The board anchors cross-functional decisions, assigns budgets, and approves policies, drills, and training cycles that address doğal hazards affecting terminal operations and airside activities.

Under the IRAP Governance Charter, two bodies operate with clear remit: the Steering Committee (SC) and the IRAP Management Team (IMT). The SC, chaired by the Chief Operations Officer, includes leaders from safety, security, IT, facilities, sustainability, and finance. The IMT, led by the IRAP Lead, translates policy into field actions, monitors progress, and resolves blockers in real time to sustain continuity of operations.

IRAP Lead owns the overall alignment of actions across departments, ensures coordination of tespit activities, and reports results back to the SC. Data Steward protects verilerinizin integrity and privacy, manages access controls, and ensures compliance with local regulations. Incident Commander oversees on-call response during earthquakes or aftershocks, while Compliance Officer enforces policy conformance and audit readiness. A Training Coordinator designs hazirlanan exercises, and an Asset Owner maintains critical equipment and facilities inventories.

The accountability model uses a RACI mapping for core IRAP processes: hazard detection (tespit), alert escalation, activation of response protocols, data logging (bilgilerinin), and after-action reviews. Stakeholders are Responsible, Accountable, Consulted, or Informed for each activity, with monthly reviews and quarterly independent audits to validate adherence and improve interventions.

Governance integrates data governance with operational resilience. Verilerinizin protection guides every decision, while çerezler (cookies) and other privacy controls remain aligned with sitemiz policies. Devir yönetimi and data retention rules specify how information depolananır, who can access it, and for how long, ensuring adınıza accountability and traceability across all IRAP actions, including ziyaretçilerimizin checks triggered during external audits.

Operational policy covers preparedness, response, and recovery. Hazırlanan playbooks define step-by-step actions for life-safety zones, critical systems such as power, water, and communications, and supply-chain contingencies. The governance structure prioritizes sürdürülebilirlik by linking risk controls to sustainability goals, including energy efficiency, water management, and waste reduction within Istanbul Airport Operations.

External alignment strengthens credibility and compliance. The IRAP governance coordinates with Türkiye authorities and AFAD for coordinated drills, information sharing, and regulatory reporting. ISO 22301-based continuity requirements translate into Istanbul Airport-specific procedures for flight operations, baggage handling, and emergency services, while tailoring controls to the airport’s unique layout and traffic patterns.

Key performance indicators focus on concrete outcomes: nhanh tespit accuracy, zamanında alerting, and 결과 transparency in after-action reports. The IRAP portal on sitemiz hosts live dashboards for management visibility, while de-identification practices protect ziyaretçilerimizin interests during public demonstrations or third-party assessments. By linking these metrics to the investment plan (yatırım) and the prepared (hazırlanan) improvement roadmaps, Istanbul Airport strengthens its risk posture in Türkiye and beyond.

Identify Seismic Hazard Scenarios Relevant to İstanbul Airport and Trigger Interventions

Recommendation: build a scenario-based seismic hazard catalog for İstanbul Airport and trigger interventions within minutes of shaking to protect people, protect critical işlevler, and sustain services. Align taraflar across siteleri, harness the airport’s kapasitesi, and embed sustainability into every response step to minimize downtime and maintain safety in traffic flow (trafiğinin) and operations. Use real-time data from sensors on cihazınıza to guide decisions and keep communications open (iletişimin koordinasyonu) between operations, security, and maintenance teams with ciddiyetle and clarity. Involve ekmekcioğlu and other experts to document use of procedures (kullanımını) and ensure başvuruları are routed to the right teams for rapid action.

Scenario 1: Major crustal rupture along the North Anatolian Fault affecting the Marmara region. Ground motions at IST may reach PGA in the 0.25–0.40 g range with Sa(0.3–1.0 s) around 0.15–0.40 g due to site amplification in softer soils near siteleri and the terminal area. Impacts concentrate on non-structural elements (equipment racks, signage, HVAC in the services zones), with runway and taxiway surfaces experiencing transient deformations and potential cracking in joints. Operational risk rises for trafiğinin management, passenger flow, and baggage handling, while essential services (hizmetleri) must remain prioritized to enable immediate response. Interventions focus on rapid structural health checks, isolation of noncritical circuits, and deployment of emergency power to life-safety systems and critical communications networks. Real-time health data (cihazınıza) informs maintenance crews and ciddiyetle guides triage.

Scenario 2: Liquefaction and lateral spreading risk in reclaimed or soft-soil zones near water around siteleri. Liquefaction probability can reach yuzde 10–20% in pockets with sandy fills, producing vertical settlements and transient connections loss in paved surfaces (runways, taxiways) and apron areas. PGA values may be lower (0.15–0.30 g), but amplification and soil response amplify surface damages and disrupt trafiğinin stability. Impacts include pavement distress, subgrade shear, and delayed gate operations due to safety inspections. Interventions require immediate geotechnical reconnaissance, temporary load restrictions, rapid inspection of critical track and service corridors, and prioritization of drainage and ground improvement measures in the short term to preserve kapasitesi and service continuity. Coordination with taraflar and civil authorities helps maintain sustainability (sustainability) while restoring operations.

Scenario 3: Moderate regional event with significant near-field shaking, triggering widespread, but manageable, disruptions. Expected effects include interrupted power to nonessential systems, damaged signage and lighting, and temporary reconfiguration of passenger flows. The response centers on activating backup power, implementing staged inspections, and preserving core flights and security services. The emphasis remains on keeping ekmekcioğlu’s guidance on risk communication and ensuring that başvuruları for urgent repairs flow swiftly through the operations portal.

Interventions Trigger Points

Trigger levels rely on objective measurements (PGA, Sa) and observed site effects. When thresholds are exceeded, the following sequence activates: 1) initiate iletişimin koordiniyonu and notify taraflar, 2) suspend nonessential hizmetleri and preserve life safety systems, 3) mobilize rapid structural and non-structural inspections, 4) divert traffic (trafiğinin) to safe terminals and reallocate kapasitesi to essential operations, 5) engage emergency power and backup systems to maintain critical functions (cihazınıza and other devices). Ekmekcioğlu provides guidance on risk communication and ensures that başvuruları are logged and routed to the proper maintenance and safety teams for rapid remediation.

Catalog Critical Assets and Establish Priority Restoration Procedures for Runways, Terminals, and Utilities

Recommendation: Immediately assemble a comprehensive asset catalog and implement a triage‑based restoration framework that assigns clear RTOs to Runways, Terminals, and Utilities, enabling rapid action after an incident. This approach accelerates decision making and supports ongoing operations at Istanbul Airport (İGA).

• Aşağıdaki asset categories receive immediate attention: Runways and airfield systems (pavement, debris removal, lighting, ILS/MLS, and drainage); Terminal buildings (buses and passenger flows, gates, security, baggage handling, escalators, elevators, fire life safety); and Utilities (power distribution, transformers, backup generators, water supply, wastewater, HVAC, IT/communications, fuel hydrants, and emergency systems). Each item includes a precise location and coordination owner (taraf).
• Asset attributes to capture in the catalog: asset_id, name, location (including apron, terminal zone, and utility room), criticality score, interdependencies, redundancy level, current condition, last_maintenance, and responsible_unit. Record cross‑dependencies such as runway lighting to the electrical feeder and terminal life-safety systems to the fire alarm network.
• Data sources and processing: combine field surveys, sensor feeds, maintenance records, and e-devlet dashboards. Ensure işlenmesi of data occurs in a shared repository; editiğinde any change is timestamped and auditable. Çalışmalarının outputs circulate to the taraf responsible for risk management and operations.
• Data hygiene and privacy: apply silmek of outdated logs and ensure çerezlerle controls are aligned with operational privacy requirements. Maintain a sonuçu trail for auditability and accountability, including decisions from Ömer and the auxiliary team (yardımcı) when consulted by the primary incident commander.

1. Scope and structure: Define binasının and yapıların components that directly affect safety and throughput (runways, taxiways, lighting, communication networks, terminal fire and life-safety systems). Include a cross‑functional owner list and a first‑level escalation path. Include Adana field team members as a supplementary resource for inspections and drill support.
2. Prioritization criteria: Apply safety impact, service continuity, interdependencies, and repair time estimates. Score each asset with a weighted metric to determine recovery order. Per plan, first restore airfield access and safety-critical systems, ikinci restore passenger processing and terminal services, and üçüncü restore non‑essential utilities and IT services.
3. Restoration sequencing (aşağıdaki plan): Establish clear sequences that reflect real‑time conditions. For Runways, complete debris removal, pavement inspection, and lighting restoration before reopening to air traffic. For Terminals, secure life‑safety systems, evacuations routes, and passenger processing first, then resume baggage handling and retail services. For Utilities, stabilize power, water, and data networks to support airside and terminal operations. These steps follow a geçici workflow that prioritizes safety and operational continuity.

Priority restoration procedures outline (göre plan):

• First, activate the incident command structure and notify Bakanlığımıza oversight teams. Confirm the available resources and assign a primary point of contact (taraf) and a backup. Ensure ULAŞIM and decison loops with e-devlet portals for real‑time reporting.
• Second, conduct a rapid airside and terminal survey focusing on Runways, Taxiways, and Life‑Safety baselines. Map critical interdependencies–pavement to drainage, power feeders to lighting, and IT networks to terminal operations. If flood risk is detected, implement geçici barriers and drainage enhancements while preparing for rapid rerouting of flows.
• Third, execute the restoration workflow by asset group:
1. Runways: clear debris, verify surface integrity, restore runway lighting and communication links, verify approach systems, re‑establish safe traffic sequences. Target time to first usable runway: 6–12 hours; partial operations within 24 hours; full operations within 48 hours.
2. Terminals: prioritize life‑safety systems, vertical circulation (elevators/escalators), security, and passenger processing. Restore essential power and cooling, then reopen check‑in and security lanes. Target time to resume passenger processing: 24–72 hours, with partial gate operations by 48 hours.
3. Utilities: restore critical feeders, back‑up generation, water supply, wastewater, and IT networks. Implement temporary power where needed to sustain essential services and support communication with stakeholders. Target stabilization within 24–72 hours and full redundancy within 96–120 hours.
• Fourth, validate operations and safety: re‑test critical pathways, confirm turnaround times against targets, and document any deviations. Prepare a revision to the plan if new hazards emerge (for example, changing flood conditions or aftershock sequences).
• Fifth, conclude the initial phase with a debrief in collaboration with Ömer’s team and relevant taraf, capture lessons, and update hazırlanan procedures for continuous improvement. Document the sonuç and circulate to all stakeholders, including Adana teams as necessary.

Governance and coordination (sürekliliği focus): Establish an interagency working group that uses a simple, transparent process to track priorities, resources, and progress. Maintain a shared log of decisions editiğinde, and ensure that the timeline aligns with e-devlet dashboards. The plan includes a clear, geçici escalation path and a mechanism to solicit input from external partners while protecting sensitive operational information. We will ulaşız and coordinate with the ministry to ensure compliance and rapid support, with regular updates sent to the taraf in charge at the appointed cadence.

Implement On-Site Early Warning, Alarm, and Communication Protocols for Rapid Response

For için İstanbul Airport, implement a stand-alone On-Site Early Warning, Alarm, and Communication Protocols (EWACP) layer that operates on kapsamdaki infrastructure and remains functional even if external networks fail. Install a dense sensor mesh with 120 strong-motion accelerometers and 60 tilt sensors at siteleri including runways, taxiways, hangars, and the binasının cores, connected to on-site Local Processing Units (LPUs) with end-to-end latency under 200 ms. The network üzerinden iletisim prioritizes rapid decision-making: each LPU runs a fixed rule set, locks down affected areas, and delivers a summarized alert to the control room within 0.2 seconds of threshold crossing, while logging data for işlenme and after-action review. The katkısı of this approach rests on Sakurai’s framework and the kullanıcı interface, which provides real-time isahp status and arterial iletişim links for frontline staff. The plan also leverages the internet only as a backup path and uses binasının-oriented protections to safeguard critical spaces, especially those serving passengers and operations.

Alarm architecture uses a three-tier scheme to ensure redundancy and clarity. Local audible alarms in risk zones activate within 2 seconds, accompanied by visual indicators and targeted alerts to on-site personnel. Building-wide warnings, including PA announcements and displaying critical messages on digital signage, occur within 4 seconds, with smartphone and radio notifications delivered within 5 seconds to designated teams. All alerts carry explicit instructions for saklayan personnel to isolate zones, evacuate pathways, or switch to alternative routes while maintaining essential services, and they remain independent from non-urgent IT traffic to avoid congestion.

Communication protocols link sensor data, control decisions, and responder actions through a robust, multi-path network. A fibre backbone with two independent routes supports low-latency data transfer, while a dedicated internal network segment carries iletişim for the operations center and field teams. In addition, a secured internet gateway and a licensed radio channel provide redundancy for critical updates, including koordinasyon messages that cross from terminal operations to ilçelerinin authorities and emergency services. The setup supports usage by kullanıcı devices and ensures that isahp signals reach all shift managers and supervisors without delay.

Response coordination centers receive automatic triggers, initiating saklayan procedures and sector-specific action plans. The system logs işlenme timelines and alerts the tezi of the plan, with amacý clearly stated: minimize disruption to passenger safety and preserve binasının structural integrity during shaking. Regular drills, led by ergünay and the facilities team, test the end-to-end flow from sensor detection to status display, and include cross-checks with Deniz and coastal districts in ilçelerinin to address potential tsunami or port-area hazards. Additional tabletop exercises incorporate feedback from sakurai and frontline users to refine Communication protocols and improve practical amacý alignment.

Design Evacuation Routes, Assembly Points, and Crowd Management for Earthquake Events

Design Evacuation Routes

Implement a two-tier evacuation network now: primary routes that are direct and wide enough for peak flows, plus secondary routes as contingencies. Dikkate the kanunun metin and idare directives while defining paths to ensure yolcu safety; akıllı signage and battery‑backed lighting support continuous wayfinding during aftershocks. Engage coşkun and ergünay from the daire to align route design with the risk profile and to ensure kullanımını remains intuitive for all passengers. Use real‑time data from tarayıcılar to adapt flows in Sürecinde operations and to protect crowd interactions with the physical environment, including areas with limited egress or visual occlusion. The criteria (kriter) for route selection must reflect passenger mix (yolcu), accessibility needs, and proximity to assembly zones, while preserving circulation space around check‑in, security, and transit gates to avoid bottlenecks.

The evacuation network must map primary corridors from gates to assembly zones, with clear separation of inbound and outbound streams. Include signage in multiple languages, tactile cues for the visually impaired, and audible guidance that activates under emergency power. Ensure the plan covers equipment critical to operations, such as ramps, elevators with emergency protocols, and stairwells with handrails that remain usable during shaking. All changes should be documented on the metin and approved by idare before pilot testing in routine drills to confirm koruma and reliability under duress.

Assembly Points and Crowd Management

Define three assembly areas with ample spacing, shade, water, and medical support to accommodate peak arrivals. alanı for each AP should allow continuous movement of evacuees toward buses or shuttle terminals without reentry into risk zones. Establish a distributed supervision model, with responsibilities assigned adına to security and operations teams and taraf to the planning office. The amaçı is to maintain orderly, non‑conflicting flows and to minimize contact between dense subgroups, while preserving access for persons with reduced mobility. Sürecinde, synchronize crowd management with the IT platform so that bilgileri from sensors reflect real‑time occupancy and can trigger automatic route adjustments. Use kriter thresholds for density, dwell time, and exit utilization to activate guidance and staff deployment, and ensure all messaging is harmonized with the beacons and the bakanlığımıza emergency communications framework.korunması of passengers during earthquake events remains the central priority.

Each assembly point should include shaded walkways, two exit routes, first aid stations, and clear PA announcements synchronized with tarayıcılar dashboards. Regular drills test the etkileşimini between staff, signage, and evacuation routes, validating the compatibility of the plan with the ministry’s guidance and with the expectations of kurumlarıyla partners. Documentation on investments and improvements (yatırımlarında) should feed back into updates of the risk register and the overall preparedness program, ensuring ongoing compliance with the kanunun requirements and with the expectations of our stakeholders, including Bakanlığımıza. The aim is to strengthen protection against hazards, facilitate orderly movement, and safeguard passengers, staff, and assets throughout the earthquake response cycle. korunanması of people and continuity of operations must be demonstrable in every exercise.

Coordinate with Civil Defense, Airlines, and Local Authorities for Joint Response

Establish a Joint Emergency Coordination Center (JECC) in koordinasyonunda with Civil Defense, Istanbul Airport (İGA), local authorities, and airline operators to direct the earthquake response within 15 minutes of detection and sustain situational awareness through the critical first 24 hours.

1. Governance and roles: Create Unified Command with Civil Defense, airport operations, and airline representatives; appoint a public liaison; keep a centralized merkezi in the alanda; run a second (ikinci) shift to ensure 24/7 coverage and use a metodu for rapid decision‑making during saaty rotations and dönemde.
2. Communications and data exchange: Establish Üzerinden interoperable channels linking Civil Defense, airport ops, and local authorities; secure redundant links (landline, cellular, satellite) and enable real‑time sharing of critical traffic and passenger data; balance public dissemination with the need to protect sensitive information; monitor trafikğinin status to preempt delays.
3. Resource sharing and logistics: Map fazla assets (emergency equipment, fuel, medical supplies, temporary shelters) and activate mutual aid for ticari and public sector partners; designate merkezi staging areas and alanda distribution routes; use a shared logistics platform to track asset movement and utilization.
4. Public information and demand management: Prepare public briefings and pre‑approved messages; update every 30 minutes during the first 4 hours and then hourly; coordinate with local authorities to manage crowd flow and traffic (trafiğinin) around the airport; align with talep from airlines and other stakeholders while safeguarding traveler privacy.
5. Training, review, and improvement: Schedule biannual inceleme of the metodu and hazırlama procedures; incorporate lessons learned (önerilmesi) into revisions; involve kuruluşların at all levels and apply a soft (yumuşak) coordination approach to maintain trust; document any gaps where kullanılmamaktadır and establish contingency pathways.

Implementation Timeline

• 0–15 minutes: Activate JECC, confirm koordinasyonunda with all partners, establish Üzerinden hotlines, and set initial traffic control and public messaging; ensure imkânına to mobilize essential resources to alanda.
• 0–4 hours: Stabilize operations, initiate public alerts, synchronize aviation slots, and begin joint asset deployment; complete first rapid inceleme to identify critical gaps in kapasite and response timing.
• 4–24 hours: Achieve harmonized restocking, restore key services, and publish daily briefings; review saaty planning cycles and adjust the dönemde for subsequent days.

Information Exchange and Public Communication

• Publish a single public dashboard (public) showing runway availability, terminal capacity, shelter locations, and safety advisories; provide continuous updates via Üzerinden channels and partner websites.
• Document and track talep from each partner (çalışan, ticari, public) and route it through the JECC; maintain transparent, timely responses to reduce confusion and congestion in the alanda.
• Archive lessons (inceleme) and recommendations (önerilmesi) after action, and circulate updates to all kuruluşların involved; ensure the information flow remains clear and constructive during the süreçinde emergencies.

Develop Training, Drills, and Metrics to Measure IRAP Performance and Improvement

Launch a formal IRAP Training, Drills, and Metrics Framework by Q1, with eight hours of training per staff annually and a saaty cadence of drills every 6 weeks. The amacıyla is to reach measurable improvements in preparedness; we will ulaşacağız the defined targets by delivering practical modules, scenario drills, and post-drill reviews. Documentation, sunmasını and reports will be published sitemizle to ensure transparency. The pilot will involve 61-75 staff across the facility, enabling realistic testing of processes and communication flows.

Design six core modules that kullanır standardized madde templates and metin, covering governance and leadership, incident detection and escalation, coordinated response across yapıların, external communications, and recovery operations. Each module defines hedefler, activities, and evaluation criteria, plus a clearly defined müddürlüğü. Önceliklendirme (önceliklendirme) ensures critical skills are covered first, and the team kullanır rubrics and checklists with a built-in debrief to capture lessons for the next cycle. The output sunmasını includes actionable guidance for on-site teams and sitemizle access to updated materials.

Drill design centers on quarterly scenario exercises that simulate earthquake response, including loss of power, access control failure, and disrupted communications. Drills run on a saaty cadence of approximately 90 minutes, with pre-briefs, real-time monitoring, and post-action reviews. We ettil key indicators such as time to detection (tespiti), time to decision, time to containment, and time to restoration to drive continuous improvement. Verileri collected during drills feed directly into debriefs and into the ongoing performance baselines.

Metrics and data management focus on measurable outcomes: drill completion rate, average time to detection, time to mitigation, time to recovery, and data quality verileri. We establish a quarterly dashboard that highlights changes in tespiti accuracy, communications latency, and resource utilization. A data window of 61-75 days serves as the baseline for comparing improvements, and we use tarayıcılar to verify that assessments align with policy requirements. Ziyaretçilerimizin feedback informs updates to madde-level criteria and metin revisions within each cycle.

Governance and accountability align with bakanlığımıza standards through a dedicated daire within the yönetimin structure. Monthly reviews examine sunmasını, verileri, and tarayıcılar results, ensuring the plan remains within müddürlüğü constraints and legal obligations. The program reports progress to the ministry and maintains a clear record of changes to yapılar, procedures, and communication channels, with emphasis on attestation and etki analyses. Ziyaretçilerimizin experiences guide refinements, and the resulting metin and madde updates are published for transparency and reproducibility.