37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 703231 |
Time | |
Date | 200607 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : abr.airport |
State Reference | SD |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : corporate |
Make Model Name | Citation II S2/Bravo |
Operating Under FAR Part | Part 91 |
Flight Phase | ground : takeoff roll |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : multi engine pilot : atp |
Experience | flight time last 90 days : 70 flight time total : 13655 flight time type : 1800 |
ASRS Report | 703231 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Events | |
Anomaly | non adherence : far |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Flight Crew Human Performance FAA Airport |
Primary Problem | Ambiguous |
Narrative:
I received and printed out a computerized standard route briefing just after XA00 am. The departure airport was abr and the destination was aoh. There was no mention of runway 13 being closed in the NOTAM section of my briefing. Approximately XB50 am; I taxied away from the FBO ramp area and stated my intentions to depart runway 13 on the only airport advisory frequency of 122.7. My taxi path paralleled runway 13; and I did not notice anything unusual or abnormal with the runway condition as I continued to the end of the runway. During the taxi; I heard an inbound aircraft and once again stated that I was proceeding to runway 13 for departure. I pulled up to the hold line at the end of runway 13 and once again made a radio call that I would be holding short of runway 13 for the landing aircraft to clear all runways. I held for several mins and continued to monitor 122.7; which during that time; I contacted ZMP on the remote ground frequency of 120.6 to obtain my IFR clearance. During those several mins of holding; I did not observe any yellow X's or any other indications in that area of runway 13 to display that it was closed. ZMP asked which runway I would be departing; which I responded with departing runway 13. I read back the clearance and once again stated to the controller that I would be departing runway 13. He responded with my 'release' and I observed that the landing traffic had cleared all runways. I made my final radio call on 122.7 stating that I was departing on runway 13. As I lined up on runway 13; my standard operation in addition to the beacon lights; is to turn on every light on the aircraft; navigation lights; strobe lights; wing ice lights; and pulsating landing and recognition lights. I noticed that there were 3 or 4 individuals and a truck off to the side of the runway but were well clear; no closer than standard airport mowing operations. Typically; at various times during taxi-outs and predeps; there has been communication with the maintenance crew and their operations on 122.7 with regard to their intentions; but this particular morning; there was no communication from the maintenance crew at any time during my taxi; hold; or runway lineup. Double-checking that there were no obstacles on the runway; I applied power and started my takeoff roll. Just as I started to rotate; there was a male voice that transmitted on 122.7 that runway 13 was closed for painting. As I made a left turnout to the northeast; I glanced back to the runway and once again; did not observe any X's or signage to indicate that the runway was closed. I then double-checked my briefing which did not mention the runway closure. When I arrived at lima; oh; 2 hours later; I called two other flight operations that departed within an hour after me. They departed on a different runway; but during their departure they also confirmed that there were no yellow X's on the runway; and one of the operators also mentioned that he did not receive the NOTAM in his briefing. However; what they observed was a red 'X' placed in the grass; in between the 2 intersecting runways; runway 13 and runway 17. In my 36 yrs in aviation; I understand that I am solely responsible for all flight preparations. In my judgement; runway 13 was normal operations based on nothing noted in the NOTAMS in my briefing. As a result of this NOTAM not posted in my briefing; and my continued dedication to aviation safety throughout my career; I have altered my standard preflight preparations to include obtaining an additional WX/airport briefing source as a 'back-up' to my normal operations. I would like to add that; whether or not all the WX services received the NOTAM in a timely manner; I feel that a backup system should also be in place to assure safe operations without solely depending on a NOTAM being published. It is my understanding that there is such a 'system' outlined in the far's; such as runway markings; or having the NOTAM recorded on the ASOS system. And to further enhance safety; as I have seen at other airports; FBO's could post a notice or reminder especially when various airport projects are underway. And then of course; it would be appreciated if maintenance crews could monitor communications to help provide a more situational and positional awareness with flight operations and aircraft ground movement. I hope this information willprove beneficial in assuring that all airport and flight operations will be conducted at a maximum safety level.
Original NASA ASRS Text
Title: A C550 FLT CREW TOOK OFF ON A CLOSED RWY AT ABR THAT WAS NOT REFED IN THEIR BRIEFING NOTAMS.
Narrative: I RECEIVED AND PRINTED OUT A COMPUTERIZED STANDARD RTE BRIEFING JUST AFTER XA00 AM. THE DEP ARPT WAS ABR AND THE DEST WAS AOH. THERE WAS NO MENTION OF RWY 13 BEING CLOSED IN THE NOTAM SECTION OF MY BRIEFING. APPROX XB50 AM; I TAXIED AWAY FROM THE FBO RAMP AREA AND STATED MY INTENTIONS TO DEPART RWY 13 ON THE ONLY ARPT ADVISORY FREQ OF 122.7. MY TAXI PATH PARALLELED RWY 13; AND I DID NOT NOTICE ANYTHING UNUSUAL OR ABNORMAL WITH THE RWY CONDITION AS I CONTINUED TO THE END OF THE RWY. DURING THE TAXI; I HEARD AN INBOUND ACFT AND ONCE AGAIN STATED THAT I WAS PROCEEDING TO RWY 13 FOR DEP. I PULLED UP TO THE HOLD LINE AT THE END OF RWY 13 AND ONCE AGAIN MADE A RADIO CALL THAT I WOULD BE HOLDING SHORT OF RWY 13 FOR THE LNDG ACFT TO CLR ALL RWYS. I HELD FOR SEVERAL MINS AND CONTINUED TO MONITOR 122.7; WHICH DURING THAT TIME; I CONTACTED ZMP ON THE REMOTE GND FREQ OF 120.6 TO OBTAIN MY IFR CLRNC. DURING THOSE SEVERAL MINS OF HOLDING; I DID NOT OBSERVE ANY YELLOW X'S OR ANY OTHER INDICATIONS IN THAT AREA OF RWY 13 TO DISPLAY THAT IT WAS CLOSED. ZMP ASKED WHICH RWY I WOULD BE DEPARTING; WHICH I RESPONDED WITH DEPARTING RWY 13. I READ BACK THE CLRNC AND ONCE AGAIN STATED TO THE CTLR THAT I WOULD BE DEPARTING RWY 13. HE RESPONDED WITH MY 'RELEASE' AND I OBSERVED THAT THE LNDG TFC HAD CLRED ALL RWYS. I MADE MY FINAL RADIO CALL ON 122.7 STATING THAT I WAS DEPARTING ON RWY 13. AS I LINED UP ON RWY 13; MY STANDARD OP IN ADDITION TO THE BEACON LIGHTS; IS TO TURN ON EVERY LIGHT ON THE ACFT; NAV LIGHTS; STROBE LIGHTS; WING ICE LIGHTS; AND PULSATING LNDG AND RECOGNITION LIGHTS. I NOTICED THAT THERE WERE 3 OR 4 INDIVIDUALS AND A TRUCK OFF TO THE SIDE OF THE RWY BUT WERE WELL CLR; NO CLOSER THAN STANDARD ARPT MOWING OPS. TYPICALLY; AT VARIOUS TIMES DURING TAXI-OUTS AND PREDEPS; THERE HAS BEEN COM WITH THE MAINT CREW AND THEIR OPS ON 122.7 WITH REGARD TO THEIR INTENTIONS; BUT THIS PARTICULAR MORNING; THERE WAS NO COM FROM THE MAINT CREW AT ANY TIME DURING MY TAXI; HOLD; OR RWY LINEUP. DOUBLE-CHKING THAT THERE WERE NO OBSTACLES ON THE RWY; I APPLIED PWR AND STARTED MY TKOF ROLL. JUST AS I STARTED TO ROTATE; THERE WAS A MALE VOICE THAT XMITTED ON 122.7 THAT RWY 13 WAS CLOSED FOR PAINTING. AS I MADE A L TURNOUT TO THE NE; I GLANCED BACK TO THE RWY AND ONCE AGAIN; DID NOT OBSERVE ANY X'S OR SIGNAGE TO INDICATE THAT THE RWY WAS CLOSED. I THEN DOUBLE-CHKED MY BRIEFING WHICH DID NOT MENTION THE RWY CLOSURE. WHEN I ARRIVED AT LIMA; OH; 2 HRS LATER; I CALLED TWO OTHER FLT OPS THAT DEPARTED WITHIN AN HR AFTER ME. THEY DEPARTED ON A DIFFERENT RWY; BUT DURING THEIR DEP THEY ALSO CONFIRMED THAT THERE WERE NO YELLOW X'S ON THE RWY; AND ONE OF THE OPERATORS ALSO MENTIONED THAT HE DID NOT RECEIVE THE NOTAM IN HIS BRIEFING. HOWEVER; WHAT THEY OBSERVED WAS A RED 'X' PLACED IN THE GRASS; IN BTWN THE 2 INTERSECTING RWYS; RWY 13 AND RWY 17. IN MY 36 YRS IN AVIATION; I UNDERSTAND THAT I AM SOLELY RESPONSIBLE FOR ALL FLT PREPARATIONS. IN MY JUDGEMENT; RWY 13 WAS NORMAL OPS BASED ON NOTHING NOTED IN THE NOTAMS IN MY BRIEFING. AS A RESULT OF THIS NOTAM NOT POSTED IN MY BRIEFING; AND MY CONTINUED DEDICATION TO AVIATION SAFETY THROUGHOUT MY CAREER; I HAVE ALTERED MY STANDARD PREFLT PREPARATIONS TO INCLUDE OBTAINING AN ADDITIONAL WX/ARPT BRIEFING SOURCE AS A 'BACK-UP' TO MY NORMAL OPS. I WOULD LIKE TO ADD THAT; WHETHER OR NOT ALL THE WX SVCS RECEIVED THE NOTAM IN A TIMELY MANNER; I FEEL THAT A BACKUP SYS SHOULD ALSO BE IN PLACE TO ASSURE SAFE OPS WITHOUT SOLELY DEPENDING ON A NOTAM BEING PUBLISHED. IT IS MY UNDERSTANDING THAT THERE IS SUCH A 'SYS' OUTLINED IN THE FAR'S; SUCH AS RWY MARKINGS; OR HAVING THE NOTAM RECORDED ON THE ASOS SYS. AND TO FURTHER ENHANCE SAFETY; AS I HAVE SEEN AT OTHER ARPTS; FBO'S COULD POST A NOTICE OR REMINDER ESPECIALLY WHEN VARIOUS ARPT PROJECTS ARE UNDERWAY. AND THEN OF COURSE; IT WOULD BE APPRECIATED IF MAINT CREWS COULD MONITOR COMS TO HELP PROVIDE A MORE SITUATIONAL AND POSITIONAL AWARENESS WITH FLT OPS AND ACFT GND MOVEMENT. I HOPE THIS INFO WILLPROVE BENEFICIAL IN ASSURING THAT ALL ARPT AND FLT OPS WILL BE CONDUCTED AT A MAX SAFETY LEVEL.
Data retrieved from NASA's ASRS site as of January 2009 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.