 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Rks airport managers closed runway 3/21 for maintenance but flight crew did not receive a NOTAM about the closure. A corporate aircraft crew requested the runway be cleared for their landing since a convenient alternate was not available. Without knowledge of a NOTAM they had not pre-planned an alternate passenger drop off point.
| Attributes | |
| ACN | 844514 |
| Time | |
| Date | 200907 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | RKS.Airport |
| State Reference | WY |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Landing |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor |
| Experience | Flight Crew Last 90 Days 50 Flight Crew Total 8500 Flight Crew Type 300 |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Ground Event / Encounter Other / Unknown |
Narrative:
While in descent; 5 min from landing; slc center advised that the runway 27/9 was now closed and the other runway (runway 21/3) that was previously closed now open. Runway 21 is too short and too narrow to use for the equipment being operated. Center advised that they just received word of the closure and that it appears that the runway had been closed for two hours. Pilots checked NOTAMS before departure (40 min flight) and none were noted. While overhead airport at 15;000 feet pilots requested the FBO people to drive out to the runway and ask if we could use the runway. FBO used the airport vehicle that had a radio for two way communication. Very good idea as we were able to confirm the situation before landing. Workers moved off the runway with their vehicles and the airport ground crew opened the runway for our use. However they did not remove the X over the runway numbers. The runway is 10;000 feet long and stopping distance and the X covering was was not a factor or consideration for operation. Pilot flying elected to land on the runway even though the X was covering the runway markers. Landing and roll out was uneventful. Also for takeoff the runway numbers were still covered and again; it was not a factor. It was greatly appreciated that the airport ground crew worked with the arrival so that the longer safer runway could be used. It was not a good idea to close the runway with an inbound aircraft so close; without checking center or FSS for filed flight plans with inbound aircraft that would need to use the runway. Rks is out in the middle of no-where so going to a nearby airport to discharge passengers was not an option. There was also a king air that was affected but he was able to land on the other runway. Suggest that before doing routine work on the runway that airport personnel check with FSS for flight plans and use other resources for establishing the arrival times of inbound aircraft or perform routine maintenance during evening or night times when traffic is non existent. Also to put out NOTAMS before hand so that pilot crews can avail themselves of the information and plan accordingly.
Original NASA ASRS Text
Title: RKS airport managers closed Runway 3/21 for maintenance but flight crew did not receive a NOTAM about the closure. A corporate aircraft crew requested the runway be cleared for their landing since a convenient alternate was not available. Without knowledge of a NOTAM they had not pre-planned an alternate passenger drop off point.
Narrative: While in descent; 5 min from landing; SLC Center advised that the Runway 27/9 was now closed and the other runway (Runway 21/3) that was previously closed now open. Runway 21 is too short and too narrow to use for the equipment being operated. Center advised that they just received word of the closure and that it appears that the runway had been closed for two hours. Pilots checked NOTAMS before departure (40 min flight) and none were noted. While overhead airport at 15;000 feet Pilots requested the FBO people to drive out to the runway and ask if we could use the runway. FBO used the airport vehicle that had a radio for two way communication. Very Good idea as we were able to confirm the situation before landing. Workers moved off the runway with their vehicles and the airport ground crew opened the runway for our use. However they did not remove the X over the runway numbers. The runway is 10;000 feet long and stopping distance and the X covering was was not a factor or consideration for operation. Pilot flying elected to land on the runway even though the X was covering the runway markers. Landing and roll out was uneventful. Also for takeoff the runway numbers were still covered and again; it was not a factor. It was greatly appreciated that the airport ground crew worked with the arrival so that the longer safer runway could be used. It was not a good idea to close the runway with an inbound aircraft so close; without checking center or FSS for filed flight plans with inbound aircraft that would need to use the runway. RKS is out in the middle of no-where so going to a nearby airport to discharge passengers was not an option. There was also a King Air that was affected but he was able to land on the other runway. Suggest that before doing routine work on the runway that airport personnel check with FSS for flight plans and use other resources for establishing the arrival times of inbound aircraft or perform routine maintenance during evening or night times when traffic is non existent. Also to put out NOTAMS before hand so that pilot crews can avail themselves of the information and plan accordingly.
Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.