 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Operational error less than standard separation when small commuter crosses runway 22R while an A300 is on takeoff roll. PF, first officer, stated reject. Captain observed the aircraft exit the runway and continued takeoff.
| Attributes | |
| ACN | 376670 |
| Time | |
| Date | 199708 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : jfk |
| State Reference | NY |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | A300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other Other |
| Flight Phase | climbout : takeoff |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | SF 340A |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground other : taxi |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 100 flight time total : 14000 flight time type : 500 |
| ASRS Report | 376670 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | controller : radar pilot : instrument pilot : flight engineer pilot : atp |
| Experience | controller military : 15 controller non radar : 15 controller radar : 15 controller supervisory : 10 flight time last 90 days : 100 flight time total : 7500 flight time type : 750 |
| ASRS Report | 377093 |
| Events | |
| Anomaly | conflict : ground less severe non adherence : required legal separation non adherence : published procedure non adherence : clearance |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | flight crew : exited adverse environment |
| Consequence | Other |
| Miss Distance | horizontal : 6000 vertical : 0 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
On takeoff roll a small commuter crossed runway 22R in our takeoff path. The incursion was about 8000 ft down runway 22R. The first officer was making the takeoff. I was head down making power adjustments. The first officer stated 'reject.' I was temporarily distraction looking at engine instruments for signs of the problem. Seeing no apparent problem, I finally looked up and saw the small commuter crossing downfield about 6000 ft from our position. As the other aircraft was exiting the runway I elected to continue the takeoff. The remainder of the flight was uneventful. This was the first time this situation has occurred for either pilot. It had a very startling effect on both of us. I need to address several specific concerns. 1) the first officer should have been more specific in his reject call. He knew what was happening but I did not. I was looking for other problems. 2) I should have been more communicative in advising him to continue the takeoff. He did not believe that course of action was unsafe but wanted to pursue the most conservative direction due to any input from me. At no time did the tower cancel our takeoff clearance. At no time did I believe that safety was jeopardized. However, communication would have led to better understanding of the situation. Supplemental information from acn 377093: as we were rolling down the runway, a commuter aircraft (type unknown) encroached on our runway. Tower told them (in excited voice) to stop. The aircraft continued to cross at taxiway J intersection. As first officer, I would now say I would've initiated reject procedures myself, the agreed upon (by captain and myself) conclusion with the safest result. Our continued takeoff was 'safe,' as far as there was enough clearance in this situation, though. More communication between captain and I would've made this situation easier to handle.
Original NASA ASRS Text
Title: OPERROR LTSS WHEN SMALL COMMUTER CROSSES RWY 22R WHILE AN A300 IS ON TKOF ROLL. PF, FO, STATED REJECT. CAPT OBSERVED THE ACFT EXIT THE RWY AND CONTINUED TKOF.
Narrative: ON TKOF ROLL A SMALL COMMUTER CROSSED RWY 22R IN OUR TKOF PATH. THE INCURSION WAS ABOUT 8000 FT DOWN RWY 22R. THE FO WAS MAKING THE TKOF. I WAS HEAD DOWN MAKING PWR ADJUSTMENTS. THE FO STATED 'REJECT.' I WAS TEMPORARILY DISTR LOOKING AT ENG INSTS FOR SIGNS OF THE PROB. SEEING NO APPARENT PROB, I FINALLY LOOKED UP AND SAW THE SMALL COMMUTER XING DOWNFIELD ABOUT 6000 FT FROM OUR POS. AS THE OTHER ACFT WAS EXITING THE RWY I ELECTED TO CONTINUE THE TKOF. THE REMAINDER OF THE FLT WAS UNEVENTFUL. THIS WAS THE FIRST TIME THIS SIT HAS OCCURRED FOR EITHER PLT. IT HAD A VERY STARTLING EFFECT ON BOTH OF US. I NEED TO ADDRESS SEVERAL SPECIFIC CONCERNS. 1) THE FO SHOULD HAVE BEEN MORE SPECIFIC IN HIS REJECT CALL. HE KNEW WHAT WAS HAPPENING BUT I DID NOT. I WAS LOOKING FOR OTHER PROBS. 2) I SHOULD HAVE BEEN MORE COMMUNICATIVE IN ADVISING HIM TO CONTINUE THE TKOF. HE DID NOT BELIEVE THAT COURSE OF ACTION WAS UNSAFE BUT WANTED TO PURSUE THE MOST CONSERVATIVE DIRECTION DUE TO ANY INPUT FROM ME. AT NO TIME DID THE TWR CANCEL OUR TKOF CLRNC. AT NO TIME DID I BELIEVE THAT SAFETY WAS JEOPARDIZED. HOWEVER, COM WOULD HAVE LED TO BETTER UNDERSTANDING OF THE SIT. SUPPLEMENTAL INFO FROM ACN 377093: AS WE WERE ROLLING DOWN THE RWY, A COMMUTER ACFT (TYPE UNKNOWN) ENCROACHED ON OUR RWY. TWR TOLD THEM (IN EXCITED VOICE) TO STOP. THE ACFT CONTINUED TO CROSS AT TXWY J INTXN. AS FO, I WOULD NOW SAY I WOULD'VE INITIATED REJECT PROCS MYSELF, THE AGREED UPON (BY CAPT AND MYSELF) CONCLUSION WITH THE SAFEST RESULT. OUR CONTINUED TKOF WAS 'SAFE,' AS FAR AS THERE WAS ENOUGH CLRNC IN THIS SIT, THOUGH. MORE COM BTWN CAPT AND I WOULD'VE MADE THIS SIT EASIER TO HANDLE.
Data retrieved from NASA's ASRS site as of July 2007 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.