37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 417590 |
Time | |
Date | 199810 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : atl |
State Reference | GA |
Altitude | msl bound lower : 26000 msl bound upper : 27000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : corporate |
Make Model Name | Gulfstream IV |
Navigation In Use | Other Other |
Flight Phase | climbout : intermediate altitude |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 150 flight time total : 7000 flight time type : 200 |
ASRS Report | 417590 |
Person 2 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 60 flight time total : 20000 flight time type : 300 |
ASRS Report | 417589 |
Events | |
Anomaly | altitude deviation : overshoot non adherence : clearance non adherence : far |
Independent Detector | atc equipment other atc equipment : unspecified other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On en route climb after departing pdk, GA, we were cleared to FL280 on a heading of approximately 250 degrees. A short time later, we were given a clearance of direct to gcv after passing FL240. After FL240 we initiated a turn for the course to gcv. Sometime during our discussion about our route, we both missed the clearance to stop our climb at FL260. With FL280 in our fgp, as we approached FL270, the controller asked our altitude. After my reply he told us to maintain FL270. He asked if we got the FL260 leveloff. I don't remember having read back such a clearance. However, there had been several vertical and lateral clrncs given in a short time frame. I could have missed it between programming our FMS and discussing our route. Before switching, the controller told us that he had lost our mode C (no specific altitude given) and when he regained mode C we were headed for FL270. We had no previous mode C complaints. Our TCASII indicated no traffic targets and there were no traffic conflicts. Our company sops are quite explicit as to vertical and lateral position awareness. The crew and controller were trying to perform too many tasks in short time line. I believe our situational awareness suffered and this event was the result. Another contributing factor that receives little or no consideration is that of leaving from airports such as pdk and being held under class B airspace 'low and slow' for 30 or 40 mi and step-climbed at 2000-3000 ft increments with multiple vectors to accommodate other traffic on sids. Complex, high performance and automated aircraft should be routed on sids as soon as possible, get into or above class B and en route to reduce exposure to this type of event.
Original NASA ASRS Text
Title: GIV GREW WERE INITIALLY ISSUED CLB TO FL280. LATER, ATC AMENDED THE ALT TO FL260, WHICH BOTH CREW MEMBERS STATE THEY HAD MISSED. THE CREW FAILED TO RESET THEIR FGP WHICH WAS SET TO FL280.
Narrative: ON ENRTE CLB AFTER DEPARTING PDK, GA, WE WERE CLRED TO FL280 ON A HDG OF APPROX 250 DEGS. A SHORT TIME LATER, WE WERE GIVEN A CLRNC OF DIRECT TO GCV AFTER PASSING FL240. AFTER FL240 WE INITIATED A TURN FOR THE COURSE TO GCV. SOMETIME DURING OUR DISCUSSION ABOUT OUR RTE, WE BOTH MISSED THE CLRNC TO STOP OUR CLB AT FL260. WITH FL280 IN OUR FGP, AS WE APCHED FL270, THE CTLR ASKED OUR ALT. AFTER MY REPLY HE TOLD US TO MAINTAIN FL270. HE ASKED IF WE GOT THE FL260 LEVELOFF. I DON'T REMEMBER HAVING READ BACK SUCH A CLRNC. HOWEVER, THERE HAD BEEN SEVERAL VERT AND LATERAL CLRNCS GIVEN IN A SHORT TIME FRAME. I COULD HAVE MISSED IT BTWN PROGRAMMING OUR FMS AND DISCUSSING OUR RTE. BEFORE SWITCHING, THE CTLR TOLD US THAT HE HAD LOST OUR MODE C (NO SPECIFIC ALT GIVEN) AND WHEN HE REGAINED MODE C WE WERE HEADED FOR FL270. WE HAD NO PREVIOUS MODE C COMPLAINTS. OUR TCASII INDICATED NO TFC TARGETS AND THERE WERE NO TFC CONFLICTS. OUR COMPANY SOPS ARE QUITE EXPLICIT AS TO VERT AND LATERAL POS AWARENESS. THE CREW AND CTLR WERE TRYING TO PERFORM TOO MANY TASKS IN SHORT TIME LINE. I BELIEVE OUR SITUATIONAL AWARENESS SUFFERED AND THIS EVENT WAS THE RESULT. ANOTHER CONTRIBUTING FACTOR THAT RECEIVES LITTLE OR NO CONSIDERATION IS THAT OF LEAVING FROM ARPTS SUCH AS PDK AND BEING HELD UNDER CLASS B AIRSPACE 'LOW AND SLOW' FOR 30 OR 40 MI AND STEP-CLBED AT 2000-3000 FT INCREMENTS WITH MULTIPLE VECTORS TO ACCOMMODATE OTHER TFC ON SIDS. COMPLEX, HIGH PERFORMANCE AND AUTOMATED ACFT SHOULD BE ROUTED ON SIDS ASAP, GET INTO OR ABOVE CLASS B AND ENRTE TO REDUCE EXPOSURE TO THIS TYPE OF EVENT.
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.