Download - Federal Aviation Administration Deer Valley Airport Runway ...dvtpilot.com/PDF/2016 RSAT DVT Local Presentation1.pdf · Runway Safety Action Team Meeting 2016 10 Federal Aviation

Local RSAT 2016

Federal Aviation Administration

Deer Valley Airport

Runway Safety Action Team Meeting

Runway Safety Action Team Meeting 2016 2 Federal Aviation Administration

Runway Safety Action Team (RSAT) • Welcome to the Team - Introduction of Team Members

Geno Riley – Air Traffic Manager – Deer Valley ATCT Ed Faron - Manager – Deer Valley Airport Stakeholders - Self Introductions (please sign roster)

• Air Traffic Operations Briefing

Runway Safety Briefing, Review of Recent Surface Incidents Status of existing Runway Safety Acton Plan (RSAP)

• Open Discussion

Share Stakeholder / User Perspective Identify Risk Factors or Current Initiatives

• Develop Runway Safety Action Plan • Adjournment


Runway Safety Action Team Process

• RSAT process • National runway incursions, severity & statistics • Review recent local incident history • Discussion of best practices • Review action items from last RSAT and determine

effectiveness • Formulate new action items for the Runway Safety

Action Plan


Surface Safety is our priority!


• Annual Runway Safety Action Team Meeting & Plan (RSAP)

• Team chaired by Air Traffic and Airport Management

• Active participation by all users/stakeholders

• Goal is to identify & reduce the risk of runway incursions

• Opportunity to take an objective look at our airport

• Acknowledge that there is room for improvement

• Commitment, dedication and ACTION for change

• Follow-up on topics that require further discussion

Local Runway Safety Action Team (RSAT) Contribution


We all know the potential damage that can be caused by a surface collision…


Changes can be made with teamwork…

• Rely on each other to break the chain of events that might lead to a runway incursion

• Each of us can contribute to find solutions

• Reducing human errors is a LARGE part of the solution

• Create mistake tolerant environment on the airfield – Redundancies to promote situational awareness


Runway Safety Action Team (RSAT)

• RSAT process • Runway incursions/excursions, distribution,

severity, statistics • Review recent incident history • Discussion of best practices • Review action items from last RSAT and

determine effectiveness • Formulate new action items for the Runway Safety

Action Plan


Definition of a Surface Incident

Unauthorized or unapproved movement within the designated

movement area (excluding runway incursions) or an occurrence in that

same area associated with the operation of an aircraft that affects or

could affect the safety of flight.


Example Vehicle crosses this marking:

Entering a Taxiway without communicating with (or receiving permission from) the Tower. “SOLID LINE = STOP” Ramp

Taxiway


Definition of Runway Incursion

An occurrence at an aerodrome involving the incorrect presence

of an aircraft, vehicle or person on the protected area of a surface designated for the landing and

take-off of aircraft.


Taxiway

Runway Example Pilot acknowledges that they are to “hold short” of the Runway, but crosses this marking anyway, entering the Runway Safety Area. “SOLID LINE = STOP”


• Breakdown in communications • Unfamiliar with airport • Loss of situational awareness • Complacency • Normalization of deviance from

process, procedures, regulations

Primary Causes of Runway Incursions


OI: Operational Incident – a surface event attributed to ATCT action or inaction. PD: Pilot Deviation - A Pilot Deviation (PD) is an action by a pilot that violates any Federal Aviation Regulation (FAR). For example, a pilot fails to comply with air traffic instructions to hold short of an active runway. V/PD: Vehicle or Pedestrian Deviation - Involves pedestrians or vehicles interfering with aircraft operations by entering or moving in the runway safety area without authorization from air traffic control.

0% 100% 0%

FY 2016 RI Statistics by Incursion Type


A large percentage of pilot deviation runway incursions involve a pilot crossing a hold line without a clearance.


Runway Incursion Severity Categories

Incident that meets the definition of runway incursion such as incorrect presence of a single vehicle, person and/or aircraft on the protected area but with no immediate safety consequences.

Category D

An incident characterized by ample time and/or distance to avoid a collision.

Category C

An incident in which separation decreases and there is a significant potential for a collision, which may result in a time critical corrective evasive response to avoid a collision.

Category B

A serious incident in which a

collision occurred or was narrowly avoided.

Category A


Runway Excursion (RE) A veer off or overrun of the runway surface.


• The majority of runway safety accidents and fatalities are runway excursions.

• Costly - Aircraft and airport property damage, airport delays - Estimated at $900 million annually

• On average, there are about 50 REs reported each month in the US.

• Excursions at airports in densely populated areas brings huge risks to airport neighbors

• By discussing and understanding RE characteristics, the hazards can be mitigated

Runway Excursions


Definition of Vehicle/Pedestrian Deviation (V/PD)

V/PD involves pedestrians or vehicles interfering with aircraft

operations by entering or moving in the runway safety area without

authorization from air traffic control.


What’s the big deal?


Because this wing…


Was once attached to this landing Citation…

Runway Safety Action Team Meeting 2016 24 Federal Aviation Administration Before it hit this tractor!!


Air Traffic Control Tower was operating. Citation was cleared to land 10 minutes out!

John Deere tractor was cleared to cross runway & had decks “up & locked” obstructing view of runway. In terms of reducing risk, a perimeter road was available.


Use great caution for areas of non- visibility ahead of & behind you!


Chicago O’Hare… dark, foggy, early morning maintenance taxi… Vehicles are instructed to give way to aircraft…


The mechanics taxiing the jet weren’t buckled in. When they hit the truck, they fell forward into the throttles – and dragged the truck a significant distance, including across an inactive runway.

ALWAYS SECURE YOUR SEATBELT BEFORE TAXI!


This was a $5 million event. The truck was a total loss, however, the driver did survive.



• RSAT process • Runway incursions, distribution, severity, statistics • Review recent incident history • Discussion of best practices • Review action items from last RSAT and determine


Action Plan


1. THE AIRCRAFT, EXITED RUNWAY 7L AND WAS INSTRUCTED TO HOLD SHORT OF RUNWAY 7R. THE PILOT READ BACK THE HOLD SHORT INSTRUCTIONS BUT CONTINUED PAST THE HOLD LINES FOR RUNWAY 7R ON TAXIWAY B9. THE GROUND CONTROLLER TOLD THE AIRCRAFT TO STOP AND THE AIRCRAFT STOPPED APPROXIMATELY 135FT SHORT OF RUNWAY 7R EDGE LINE.

2. A/C 1/P28A AND A/C 2/P28A BOTH CALLED READY FOR DEPARTURE AT RUNWAY 7R. LOCAL CONTROL INSTRUCTED A/C 2 TO LINE UP AND WAIT. A/C 1 READ BACK THE INSTRUCTIONS AND TAXIED ONTO THE RUNWAY. LC DID NOT CATCH THE INCORRECT READ BACK. LC THEN CLEARED A/C 2 FOR TAKEOFF. A/C 1 READ BACK THE INSTRUCTIONS AND DEPARTED. LC AGAIN DID NOT CATCH THE INCORRECT READ BACK. LC WAS MADE AWARE OF THE SITUATION WHEN A/C 2 ADVISED THEY WERE STILL HOLDING SHORT.

3. PA31 AWAITING DEPARTURE C3/7R INSTRUCTED TO HOLD SHORT READ BACK WAS CORRECT. A/C CROSSED HOLD SHORT LINES.

RUNWAY INCURSIONS


4. #2 AIRCRAFT WAS GIVEN TAXI

INSTRUCTIONS TO RWY 25L INT C12 AND TOLD TO REMAIN ON GROUND FREQUENCY DUE TO RUNWAY CHANGE. #1 AIRCRAFT WAS TOLD TO FLY STRAIGHT OUT AND CLEARED FOR TAKEOFF RWY 7R. LOCAL SOUTH SAW #2 AIRCRAFT START TO TAKE RWY 25L AND TOLD HIM TO STOP AFTER AIRCRAFT HAD CROSSED HOLD BARS. #1 AIRCRAFT WAS MID FIELD UPWIND WITH ANOTHER AIRCRAFT IN POSITION FOR TAKEOFF RWY 7R. #2 AIRCRAFT WAS TAXIED OFF THE ACTIVE RUNWAY AND WAS GIVEN THE BRASHER WARNING PRIOR TO TAXI BACK TO RAMP

5. AIRCRAFT WAS TAXIED TO RWY 7R C3. UPON REACHING INTERSECTION C3 THE CESSNA PULLED PAST THE HOLD BARS ONTO RWY 7R. WAS TOLD TO MAKE A 180 DEGREE TURN AND PULL BACK INTO CHARLIE 3

6. AIRCRAFT EXITED RUNWAY 25R AT BRAVO 9, THE AIRCRAFT WAS INSTRUCTED TO HOLD SHORT OF RUNWAY 25L. THE PILOT READ BACK THE HOLD SHORT INSTRUCTIONS, THEN PROCEEDED TO CROSS THE HOLD SHORT LINE AS THE CONTROLLER INSTRUCTED HIM TO HOLD POSITION.

RUNWAY INCURSIONS


7. AIRCRAFT WAS IN THE NORTHWEST RUN-

UP AREA AND HAD COMPLETED HIS RUN-UP. PILOT CALLED GROUND CONTROL FOR TAXI TO THE RUNWAY. GROUND CONTROL ISSUED THE TAXI INSTRUCTION TO RUNWAY 7L. AIRCRAFT TAXIED FROM THE NORTHWEST RUN-UP AREA TO RWY 7L BUT DID NOT STOP AT THE RWY HOLDSHORT MARKINGS. INSTEAD, ENTERED RWY 7L AT TAXIWAY A4 AND STARTED DEPARTURE ROLL. AIRCRAFT NOTICED THAT HE HAD ENTERED THE RUNWAY WITHOUT CLEARANCE, STOPPED AND CALLED TOWER.

8. AIRCRAFT HAD CROSSED RWY 25R AT ALPHA 11 AND WAS INSTRUCTED TO HOLDSHORT OF RWY 25L. AIRCRAFT DID INITIALLY STOP AT THE HOLDSHORT LINES FOR RWY 25L BUT THEN STARTED TO TAXI AGAIN MOVING PAST THE HOLDSHORT BARS. AIRCRAFT STOPPED ABOUT 20FT PAST THE RWY 25L HOLDSHORT BAR BUT PRIOR TO THE RWY EDGE LINE. THE PILOT OF THE TAXIING AIRCRAFT STATED THAT HE SAW THE AREA WHERE THE OLD HOLD BARS USED TO BE.

RUNWAY INCURSIONS


9. PC-12, REPORTED 5.5 NM NORTHEAST OF DVT INBOUND TO LAND. STATED THAT HE WAS CLEARED FOR THE VISUAL FOR RWY 7R BUT REQUESTED TO LAND RWY 7L. PILOT INSTRUCTED TO MAKE LEFT TRAFFIC FOR RWY 7L THEN WAS CLEARED TO LAND ON RWY 7L AND READ BACK THE CLEARANCE CORRECTLY. AIRCRAFT LANDED RWY 7R AND EXITED AT TAXIWAY CHARLIE 7.

10. AIRCRAFT WAS AT RWY 7R AND CHARLIE 1. CALLED READY FOR DEPARTURE AND THE LOCAL SOUTH CONTROLLER INSTRUCTED AIRCRAFT TO LINE-UP-AND-WAIT ON RWY 7R. READ BACK THE LUAW INSTRUCTIONS CORRECTLY. #2 AIRCRAFT WAS THEN INSTRUCTED TO CROSS RWY 7R AT TAXIWAY CHARLIE 9 BY GROUND CONTROL. AFTER GIVING THE CROSSING INSTRUCTION, THE GROUND CONTROLLER SCANNED THE RWY AND NOTICED THAT THE AIRCRAFT THAT WAS LUAW WAS ROLLING ON RWY 7R. THE GROUND CONTROLLER NOTIFIED THE LOCAL SOUTH CONTROLL

RUNWAY INCURSIONS


11. AIRCRAFT WAS TAXIED FROM THE NORTH RAMP TO THE NORTHWEST RUN-UP AREA. AFTER COMPLETING HIS RUN-UP, THE PILOT CALLED GROUND CONTROL AND WAS TAXIED TO RWY 7L VIA TAXIWAYS ALPHA, ALPHA4. PILOT READ BACK THE TAXI INSTRUCTIONS WITHOUT READING BACK THE RWY ASSIGNMENT. GROUND CONTROL TRIED A NUMBER OF TIMES TO GET THE AIRCRAFT TO READ BACK THE RWY ASSIGNMENT WITH NO RESPONSE. PILOT TAXIED TO RWY 7L AT TAXIWAY ALPHA4 AND CROSSED THE HOLD POSITION MARKINGS.

12. AIRCRAFT LANDED RWY 7L AND TURNED RIGHT AT THE END ONTO TWY B11. PILOT WAS INSTRUCTED TO TAXI VIA B AND B9 AND TO HOLD SHORT OF RWY 7R. PILOT TURNED LEFT ONTO B9 AND CONTINUED TO TAXI ACROSS THE HOLDBARS FOR RWY 7R AND WAS THEN INSTRUCTED TO STOP. AIRCRAFT STOPPED APPROX. 200 FEET FROM THE EDGE OF RWY 7R. THERE WAS AN ARCHER AIRBORNE OFF RWY 7R ABEAM TWY C7 (APPROX 1250 FEET FROM THE INTERSECTION OF TWY B9). A CESSNA HAD BEEN CLEARED FOR TAKEOFF RWY 7R AT TWY C1 BUT THEIR CLEARANCE WAS CANCELLED.

RUNWAY INCURSIONS


13. AIRCRAFT LANDED RWY 7L AND EXITED AT TWY B9. AIRCRAFT DID NOT CONTINUE PAST THE RWY HOLD SHORT MARKINGS FOR RWY 7L. GC INSTRUCTED THE PILOT TO CONTINUE ACROSS THE HOLD SHORT MARKING FOR 7L AND HOLD SHORT OF RWY 7R ON TWY B9. AIRCRAFT CAME TO A COMPLETE STOP ON THE CORRECT SIDE OF THE HOLD SHORT MARKING FOR RWY 7R BUT THEN CONTINUED FORWARD ACROSS THE HOLD SHORT OF RWY 7R. GC INSTRUCTEDTHE PILOT TO STOP AND THE AIRCRAFT CAME TO A STOP BEFORE CROSSING THE RWY EDGE LINE .

14. A P28A HAD BEEN CLEARED FOR TAKEOFF ON RWY 25L FROM FULL LENGTH. IMMEDIATELY AFTER ISSUING THE CLEARANCE, THE LOCAL SOUTH CONTROLLER NOTICED A FLIGHT OF 3/UH60 HELICOPTERS CROSSING THE HOLD BARS AT TAXIWAY CHARLIE8 AND PROCEEDING ONTO RWY 25L. THE LOCAL CONTROLLER IMMEDIATELY WENT BACK TO THE DEPARTING, WHO HAD NOT STARTED TAKEOFF ROLL, AND CANCLED THEIR DEPARTURE CLEARANCE AND INSTRUCTED THEM TO HOLD IN POSITION.

RUNWAY INCURSIONS


15. AIRCRAFT LANDED RWY 7L AND WAS TOLD TO EXIT AT THE END ON TWY B11. HE DID NOT STOP AFTER EXITING AND CONTINUED TO TAXI ON B11 TOWARDS RWY 7R. HE CALLED GC AS HE WAS TAXIING AND GC ASKED WHERE HE WAS GOING. HE REPLIED THE HE WAS TAXIING IN BUT DID NOT HOLD SHORT OF RWY 7R. .

16. AIRCRAFT CHECKED IN FROM THE SOUTHEAST REQUESTING RWY 7L. LOCAL SOUTH ISSUED RUNWAY 7L AND THE LOCAL NORTH CLEARED AIRCRAFT TO LAND 7L, THE AIRCRAFT LANDED 7R.

17. AIRCRAFT WAS TAXID TO RWY 7L. AIRCRAFT CROSSED THE HOLDBARS WITHOUT CLEARANCE CAUSING THE LOCAL NORTH CONTROLLER TO SEND AIRCRAFT SHORT FINAL AROUND.

RUNWAY INCURSIONS


1. SUMMARY: AIRCRAFT WAS OBSERVED TAXIING ON TWY "C" TOWARD RWY 7R. AIRCRAFT DID NOT CALL GROUND OR TOWER PRIOR TO TAXI. AIRCRAFT CALLED LCS 118.4 PRIOR TO REACHING THE RWY. AIRCRAFT WAS INSTRUCTED TO CONTACT GC AS THEY HAD AN IFR CLEARANCE ON FILE. GC READ THE CLEARANCE AND ISSUED THE BRASHER WARNING. PILOT DID NOT CALL THE FACILITY

2. GROUND CONTROL NOTICED AN AIRCRAFT ENTER TAXIWAY CHARLIE WITHOUT RECEIVING TAXIN INSTRUCTIONS. GROUND CONTROL AND BOTH LOCAL CONTROLS ATTEMPTED TO CONTACT THE AIRCRAFT WITH NO RESPONSE. THE AIRCRAFT FINALLY MADE A TRANSMISSION ON 118.4 AND THE LOCAL SOUTH CONTROLLER REACHED OUT TO THE AIRCRAFT AFTER SPEAKING WITH HE STATED THAT ONE OF HIS TWO RADIOS APPEARS NOT TO BE WORKING CORRECTLY . HE ALSO STATED THAT HE DID TRY TO CONTACT GROUND.

TAXIWAY INCURSIONS


3. AIRCRAFT LANDED RWY 7R AND WAS INSTRUCTED TO TURN LEFT OFF THE RUNWAY AT B9 (THEY WANTED TO TAXI TO THE NORTH SIDE OF THE AIRPORT). AIRCRAFT EXITED ONTO B9 AND CONTINUED TAXIING NORTHBOUND WITHOUT CLEARANCE ACROSS TAXIWAY B AND HELD SHORT OF RWY 7L BLOCKING THE PRIMARY RWY 7L EXIT POINT. THERE WAS AN AIRCRAFT THAT LANDED RWY 7L THAT WAS EXPECTING TO EXIT THE RWY AT B9. THE LANDING AIRCRAFT WAS HELD ON RWY 7L TO ALLOW THE TAXIING AIRCRAFT TO TAXI ACROSS RWY 7L.

4. SUMMARY: AIRCRAFT LANDED RWY 25R AND EXITED AT A6. TAXIED ON TO TWY A WITHOUT CLEARANCE AND CONTINUED WEST BOUND UNTIL LOCAL NORTH CONTROLLER STOPPED THE AC AND TOLD HIM AGAIN TO CONTACT GROUND CONTROL.

TAXIWAY INCURSIONS


1. AIRCRAFT WAS TAXIING TO RWY 25L ON TWY C. GC/CIC WAS GETTING THE HOURLY TRAFFIC COUNT AND LOOKED UP TO NOTICE THE ACFT IN THE ROCKS BETWEEN TWY C AND THE RAMP. THE PILOT KEYED UP AND SAID SOMETHING ABOUT JET BLAST. THERE WAS A GL5T STARTING UP ON THE RAMP IN THE VICINITY. AIRPORT OPS WAS NOTIFIED TO ASSIST THE ACFT OFF THE ROCKS AND INTO THE RAMP. NO DAMAGED WAS REPORTED AND THE ACFT TAXIIED BACK TO PARK VIA THE RAMP.

2. C172 WAS DOING FULL STOP TAXI BACKS ON RUNWAY 7L AND SLID OFF THE RUNWAY AND IN TO THE ROCKS WEST OK INTERSECTION A8. PILOT WAS ABLE TO TAXI AIRCRAFT BACK

EXCURSIONS


3. AIRCRAFT LANDED RWY 7R AND EXITED THE RUNWAY AT TWY C6 AND SUBSEQUENTLY RAN OFF THE LEFT EDGE OF TWY C6 AND STOPPED 10 FEET INTO THE ROCKS AND PAST THE HOLDBARS. AIRCRAFT SHUT DOWN AND WAS TOWED TO THE RAMP. 1 TWY EDGE LIGHT WAS BROKEN AND THERE WAS NO DAMAGE TO THE ACFT.

4. AIRCRAFT WAS ON TAKEOFF ROLL AND LOST CONTROL OF AIRCRAFT AND WENT INTO THE INFIELD ROCKS APPROXIMATELY C3/B3. PILOT WAS ABLE TO REGAIN CONTROL OF THE AIRCRAFT AND EXITED THE RUNWAY AT C5. TRANSPAC AVIATION REPORTED PROP STRIKE WITH NO INJURIES.

EXCURSIONS


5. C172 WAS LANDING RUNWAY 7R. THE AIRCRAFT UNINTENTIONALLY EXITED RUNWAY 7R TO THE RIGHT PRIOR TO TAXIWAY C5 AND CAME TO REST IN THE ROCKS JUST PAST TAXIWAY C6. AIRCRAFT ADVISED THAT HE COULD TAXI TO THE RAMP UNDER HIS OWN POWER. WESTWIND, THE SCHOOL THAT OWNS THE AIRCRAFT, CALLED AND STATED THAT THERE WAS NO DAMAGE TO THE AIRCRAFT.

6. LCS INSTRUCTED THE PILOT, WHO WAS AT TAXI SPEED, TO EXIT RWY 25L AT C6. PILOT RESPONDED WITH "WILCO", AND THEN ADVISED THAT THEY WERE NOT ON THE TAXIWAY. THE PILOT THEN RE-MANEUVERED ONTO RUNWAY 25L THEN EXITED AT C6 UNDER THEIR OWN POWER. NO ASSISTANCE WAS NEEDED. RWY 25L TEMPORARILY CLSD FOR FOD CHECK, THEN REOPENED PER CITY OPS.

EXCURSIONS


7. AIRCRAFT CAME INBOUND FROM THE NW TO LAND AT DVT. THE PILOT STATE THAT HE DID HAVE THE CURRENT ATIS AND WAS INSTRUCTED TO MAKE RIGHT TRAFFIC FOR RWY 25R. AIRCRAFT WAS LANDING ROLL ON RWY 25R AND AT TAXIWAY BRAVO9 THE AIRCRAFT VEERED OFF THE LEFT SIDE OF THE RWY. WENT THROUGH THE INFIELD AREA BETWEEN RWY 25R AND THE PARALLEL TAXIWAY BRAVO EVENTUALLY GETTING THE AIRCRAFT UNDER CONTROL AND ROLLING OUT ON TAXIWAY BRAVO WHERE HE STOPPED.

EXCURSIONS





Action Plan


Routinely check airport diagrams for accuracy and update as needed

BEST PRACTICES


Tours of the tower cab as part of pilot training, driver training, and tenant familiarization


What are the benefits of controllers, pilots & drivers participating in airfield tours, or runway

inspections?


Airfield Tours will give insight on preferred routes, time required on movement areas, FOD issues, line of sight, etc.


Are contractors aware of the inherent dangers? Are contractors aware of haul routes and restricted areas?

Have the contractor personnel visited the tower? Have the contractors taken the driver training course?

Training and close monitoring of contractor personnel conducting work on the airport


Enforced use of service roads minimize use of runways and taxiways by vehicles/equipment


Signage at all vehicle entry points to the AOA and runway safety areas


Well maintained perimeter fence


Are vehicle & pedestrian gates secure?

Make sure only authorized personnel can access the movement areas!

Don’t let Jimmy Johns use your taxiways as a shortcut for their “Freaky Fast Delivery!” as they did at a towered Michigan airport in 2012.


Mandatory seat belt usage for ALL individuals who reposition aircraft


Best Practice: INFORMING AFSS ANY TIME THERE IS CHANGE IN YOUR RUNWAY STATUS Advocate & practice situational awareness and

risk reduction in the cockpit, tower or vehicle


FAR 121.542 or FAR 135.100 Flight Crewmembers duties

Sterile cockpit and heads up during taxi


All lights on for takeoff and landing AC 173


Runway Safety Action Team (RSAT) • RSAT process • Runway incursions, distribution, severity, statistics • Review recent incident history • Discussion of best practices • Review action items from previous RSAT meetings

and determine effectiveness • Formulate new action items for the Runway Safety

Action Plan


Action Item Code: DVT-2013-001

Status : Not Funded

Completion Date: 9/30/15 (estimated)

Action Item: Investigate the feasibility of adding two Local Assist positions of operation in the air traffic control tower.

Action Item Rationale:

Having two Local Assist controller positions in the tower would greatly lower the chances of a runway incursion created by crossing in the high energy segment of the runway and address hot spot issues. The extra set of eyes that a Local Assist person would provide not only increases vigilance for an inadvertent crossing of a runway, but also lowers controller coordination requirements when crossings are needed.

Point of Contact: Deer Valley Air Traffic Control Tower----Geno Riley--Deer Valley Air Traffic Control Tower----(623) [email protected]

Last Update Date: 3/24/2015

Last Status Update/Status Clarification:

New ATM 60 days has dropped pursuit of additional positions as they would not be funded. Crossing test began on change procedure switching to ground between runways. Ending mid October and results evaluated then.



Status : On Course


Action Item:

Deer Valley Air Traffic Control Tower plans to schedule a meeting with the Warbird Squadron Commander to discuss current procedures and possible changes to those procedures to ensure safe and efficient arrivals.


Point of Contact: DVT ATM----Geno Riley--DVT [email protected]



ATCT email dated 4/21/2016 reported: Deer Valley Air Traffic Control Tower is working to schedule a meeting with the Warbird Squadron Commander to discuss current procedures and possible changes to those procedures to ensure safe and efficient arrivals.



Status : Completed

Completion Date: 4/21/16 (actual)

Action Item:

Deer Valley Air Traffic Control Tower understands the need for on-the-stop correction and education of the student pilot community. The tower has developed a pilot briefing for the students and instructor pilots on the field; they plan to present a monthly class.

Action Item Rationale: Providing on-the-spot correction to student pilots when an incorrect read-back is noticed.




DVT email dated 4/21/2016 reports this item complete with the following comment: DVT is continuing to provide on-the-spot correction to student pilots when an incorrect read-back is noticed.



Status : Completed

Completion Date: 4/21/16 (actual)

Action Item:

Deer Valley Air Traffic Control Tower has developed a pilot briefing for the students and instructor pilots on the field. Through this forum, the tower plans to clear up any confusion and questions the pilots have


This will be an educational class touching on topics such as runway safety and best practices within the Deer Valley Class Delta Airspace.




DVT ATCT email dated 4/21/2016 reports this item is complete with the following comment: Deer Valley Air Traffic Control Tower has developed a pilot briefing for the students and instructor pilots on the field. We have provided several briefings since the LRSAT.



Status : On Course


Action Item:

The Emergency Letter of Agreement between the City of Phoenix and Phoenix-Deer Valley Air Traffic Control Tower is in the process of being updated. We are unable to complete this action item until the airport diagram is updated with Taxiways A6 and A8.


Upon completion and submission of the new LOA, the City of Phoenix Fire Department will begin training the closest fire house crews on airport emergency response procedures to ensure response is timely and efficient.

Point of Contact: ATM----Geno Riley--DVT [email protected]



DVT ATCT email dated 4/21/2016 reported: The Emergency Letter of Agreement between the City of Phoenix and Phoenix-Deer Valley Air Traffic Control Tower is in the final stages. DVT ATCT is awaiting signatures by the other parties.


Think about the previous action items

• Was the risk mitigated? • Are the same problems still

occurring? • Did the mitigation cause

other problems?

• Does something else need to be considered?


Make sure your action items are “SMART”





Action Plan


Airport Geometry

• Crossings in middle third of runway (high-energy areas)

• Unusual marking and/or signage placement

• Absence of a full length parallel taxiway

• Direct/short ramp to runway taxi routes

• Aligned taxiways (in-line)

• Intersections with more than three ways to go

• Wide expanse of pavement at a taxiway/runway intersection

• Entrance taxiways at other than 90º to runway

• Taxiway coinciding with the intersection of two runways

Does the airport have any of these common geometry problems?


Airport Geometry

• Are there airport geometry changes planned aimed at reducing the risk of runway incursions?

• Are there procedural or other mitigations needed to reduce risk? • Prohibiting crossings in high energy segment of

runways • Runway guard lights at difficult intersections • Surface painted signs at difficult intersections


Construction Discussion • Is construction planned that impacts aircraft

surface operations?

• Back taxi or extra runway crossings

• Shortened or closed runways

• Unusual or temporary hold line locations


What have you experienced on the airport that concerns you?

Are there any areas that could be at high risk for an Incident/Incursion?

Can you identify any procedures that could be improved? (such as Airport Maintenance (snow removal/grass cutting), Security of gates, FOD removal, Airport Paint & Signage, Airport Lighting, Air Traffic procedures)


Distribution of runway safety materials to pilots, construction contractors, and vehicle operators


Visit us at www.faa.gov/go/runwaysafety There are training animations, videos and a link to order printed training materials.

http://www.faa.gov/go/runwaysafety


For Air Traffic Concerns:

• Geno Riley, Air Traffic Manager , DVT ATCT • (623)581-1492 • Mike Beauvais, Support Specialist, DVT ATCT • (623)581-1492


THANK YOU FOR YOUR PARTICIPATION!

All team members will be emailed a copy of the Runway Safety Action Plan

Download - Federal Aviation Administration Deer Valley Airport Runway ...dvtpilot.com/PDF/2016 RSAT DVT Local Presentation1.pdf · Runway Safety Action Team Meeting 2016 10 Federal Aviation

Top Related