37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 967259 |
Time | |
Date | 201108 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | NCT.TRACON |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Cessna Citation Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | SID SKYLINE 3 |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Conflict Airborne Conflict Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
We were cleared via the skyline 3 departure from oak. Prior to departure from runway 29 we reviewed the departure procedure that was entered in the FMC. We went over all the points; including staying at or below 2;000 ft until passing 4.0 DME of oak. At some point; unknown to me; the captain had changed the departure procedure by adding a 135 radial and distance to define the porte intersection off pye. After being cleared for takeoff we departed with a shallow climb to meet the restriction. Immediately after departure; we had a very close TA that distracted our attention; and tower told us to contact nct departure at the same time. Departure immediately cleared us to climb unrestricted to 10;000 MSL. A very short time later ATC informed us of a possible altitude deviation at the 4.0 DME.later; when out of sterile cockpit we discussed the situation. The captain suggested the altitude deviation may have been caused by him adding the point; bearing; and distance to define the porte intersection. The departure procedure altitudes were reviewed and the 2;000 at 4.0 DME was recognized. However; we believe the route modification to define porte may have removed the altitude from the departure procedure thus eliminating an altitude warning for the 4.0 DME. Also the TA distraction initially prevented us from paying closer attention to the restriction. We are unaware if there was an altitude deviation; but since ATC gave us an unrestricted climb and mentioned the 4.0 DME and altitude; and made a short mention of san francisco's class B airspace; that perhaps there was a violation. There are no other deviations to mention at this time. I believe our crew suffered from task saturation; fatigue; and a non-standard programming of the FMC which contributed to the situation above. After the discussion of the matter we agreed we will inform each other of any changes made to the FMC. This will create communication and a review of the procedure so if any changes are made to the departure they will be caught and dealt with prior to actually flying the aircraft.
Original NASA ASRS Text
Title: A CE-750 flight crew failed to comply with the 2;000 MSL at 4.0 DME restriction on the SKYLINE SID off Runway 29 at OAK. Inappropriate FMS route alterations and distractions from a TA shortly after takeoff may have contributed.
Narrative: We were cleared via the Skyline 3 departure from OAK. Prior to departure from Runway 29 we reviewed the departure procedure that was entered in the FMC. We went over all the points; including staying at or below 2;000 FT until passing 4.0 DME of OAK. At some point; unknown to me; the Captain had changed the departure procedure by adding a 135 Radial and distance to define the PORTE Intersection off PYE. After being cleared for takeoff we departed with a shallow climb to meet the restriction. Immediately after departure; we had a very close TA that distracted our attention; and Tower told us to contact NCT Departure at the same time. Departure immediately cleared us to climb unrestricted to 10;000 MSL. A very short time later ATC informed us of a possible altitude deviation at the 4.0 DME.Later; when out of sterile cockpit we discussed the situation. The Captain suggested the altitude deviation may have been caused by him adding the Point; Bearing; and Distance to define the PORTE Intersection. The departure procedure altitudes were reviewed and the 2;000 at 4.0 DME was recognized. However; we believe the route modification to define PORTE may have removed the altitude from the Departure Procedure thus eliminating an altitude warning for the 4.0 DME. Also the TA distraction initially prevented us from paying closer attention to the restriction. We are unaware if there was an altitude deviation; but since ATC gave us an unrestricted climb and mentioned the 4.0 DME and altitude; and made a short mention of San Francisco's Class B Airspace; that perhaps there was a violation. There are no other deviations to mention at this time. I believe our crew suffered from task saturation; fatigue; and a non-standard programming of the FMC which contributed to the situation above. After the discussion of the matter we agreed we will inform each other of any changes made to the FMC. This will create communication and a review of the procedure so if any changes are made to the Departure they will be caught and dealt with prior to actually flying the aircraft.
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.