2010-10 · NASA ASRS report 912283
RDU Controller providing OJT experienced airspace deviation when departure traffic leveled at lower than cleared altitude; confused by chart notations; which led to the confused airspace coordination event.
The leading factors began on initial RADAR Contact. The trainee did not recognize the aircraft stopped his climb at 20. Normal jet departures climb to 70. I allowed time for the trainee to observe this; however we began to get busy with more departures. I stepped in and asked the pilot to confirm his altitude. The pilot verified 20; which was a misunderstanding of the Departure Procedure. Note (not the first time this has happened) I instructed the aircraft to climb to 120; which is the normal altitude to deliver aircraft to the Center. For whatever reason; the trainee took the aircraft out of hand off status; and pointed the aircraft out to FAY Approach Control. I did not catch this mistake as quickly. The aircraft was out of 105 when I observed the aircraft was no longer automating to Center. I instructed the aircraft to maintain 100 and began coordinating with the Center. The Center said to put the aircraft on a 100 heading due to an active ALTRA. The trainee turned the aircraft to a 100 heading; however the aircraft was in Fayetteville's airspace. We did not have control for turns. I should have taken over from the trainee much sooner and departure procedure needs to be re-written. We have had numerous misunderstandings due to poorly written departure procedures.
Our mission was to ferry a C560 from Raleigh Durham International Airport (RDU). I was the pilot in command and the pilot flying. The Co-Pilot received clearance (cleared as filed; FAY3.FAY; climb and maintain 070; expect FL320 in 10 minutes). He reviewed the clearance with me and we got taxi clearance to the active Runway 23R. On taxi we dialed in 7;000 in the altitude and 232 degrees for the heading. While holding for our sequence for take off; we reviewed the FAY3.FAY SID again and noted the initial climb procedures that instructs a climb on heading 232 degrees to 1;800 FT. I reset the altitude to level off at 1;800 FT MSL. We departed once receiving take off clearance flew the FAY3.FAY SID (232/1;800 FT MSL) and leveled off as published. Traffic communications were very congested so we could not get clarification with departure for a climb to 7;000 FT MSL as per our clearance. This is where we made our mistake. I was unsure if ATC expected us to climb directly to 7;000 FT or level off at 1;800 and wait for departure to instruct us to climb. I understand that once given an ATC clearance that this now supersedes SID restrictions as per my conversion with a RDU Supervisor. As a crew we will get solid clarification from ATC of routing and altitude restrictions prior to take off. This mistake will be discussed at our next pilot meeting and discussed to enhance flying safety.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.