37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1037632 |
Time | |
Date | 201209 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | TEB.Airport |
State Reference | NJ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Cessna Citation Sovereign (C680) |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | SID RUUDY4 |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Private Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 550 Flight Crew Type 25 |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Miss Distance | Horizontal 12000 Vertical 500 |
Narrative:
While departing on the teb ruudy 4 departure; we received both a traffic advisory from ATC and from our TCAS system about a plane flying below us; opposite direction. I was the pilot flying and elected to keep my nose down at about 1400 feet in order to maintain visual separation with traffic. The ruudy 4 calls for 1500 feet until wentz. TCAS was telling us that the plane was about 2 miles away and at 1000 feet or so (or there abouts; things were moving fast!). The PIC on the plane (I currently hold an soe restriction) indicated to me after the incident that I should have been at 1500 feet as per the SID. After thinking about it and interpreting the rules I agree. My rush to think about keeping visual separation; while important; trumped my thoughts [to] follow the dp as it was designed. We knew that teb tower was in contact with our traffic and we were with ny tracon; so separation was always assured and was never violated in this instance; even despite the lower altitude. Quick thinking would have yielded better results in this case. With everything happening so fast; one has to know all the rules of the road to prepare quickly. They create departure procedures for a reason and adherence to them is paramount; unless in the event of RA advisory which did not occur. No sooner then I realized I had leveled off too early; ny TRACON has us climbing. I am now however better prepared for this type of situation and learned more regarding the rules of SID's.
Original NASA ASRS Text
Title: CE680 First Officer reports crossing WENTZ below the RUUDY 4 depicted altitude due to a traffic advisory although the traffic was at 1000 feet.
Narrative: While departing on the TEB RUUDY 4 DEP; we received both a traffic advisory from ATC and from our TCAS system about a plane flying below us; opposite direction. I was the pilot flying and elected to keep my nose down at about 1400 feet in order to maintain visual separation with traffic. The RUUDY 4 calls for 1500 feet until WENTZ. TCAS was telling us that the plane was about 2 miles away and at 1000 feet or so (or there abouts; things were moving fast!). The PIC on the plane (I currently hold an SOE restriction) indicated to me after the incident that I should have been at 1500 feet as per the SID. After thinking about it and interpreting the rules I agree. My rush to think about keeping visual separation; while important; trumped my thoughts [to] follow the DP as it was designed. We knew that TEB Tower was in contact with our traffic and we were with NY Tracon; so separation was always assured and was never violated in this instance; even despite the lower altitude. Quick thinking would have yielded better results in this case. With everything happening so fast; one has to know all the rules of the road to prepare quickly. They create departure procedures for a reason and adherence to them is paramount; unless in the event of RA advisory which did not occur. No sooner then I realized I had leveled off too early; NY TRACON has us climbing. I am now however better prepared for this type of situation and learned more regarding the rules of SID's.
Data retrieved from NASA's ASRS site as of July 2013 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.