37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1176981 |
Time | |
Date | 201406 |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Route In Use | STAR GIBBZ |
Component | |
Aircraft Component | Seat Belt Sign |
Person 1 | |
Function | Captain Pilot Flying |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural FAR |
Narrative:
The gibbz arrival is a very busy arrival and it was even busier than usual that day. I got distracted both by the approach and the added distractions of two close encounters with VFR traffic and many turns and descents from ATC at a busy time of the arrival. We landed with the seat belt sign off. Passing through FL180 we were distracted by the busy gibbz arrival. Just as we were passing through 10;000; where I would usually check the seatbelt sign; we were given our runway assignment and it was not what we had expected (we were given [runway] 19R) and we were given what sounded like an urgent traffic alert with a turn off the arrival to avoid VFR traffic. We also had to call the flight attendant; because we didn't have a sterile light. Then; as we were trying to prepare for the approach to runway 19R we were given another turn back towards the airport; then a frequency change. On checking in we were given another traffic alert of a VFR target less than 2 miles and 500 ft above our assigned altitude. We picked up this traffic visually just as the resolution advisory was being enunciated. We called and kept the traffic in sight visually until we were clear of conflict; then finished the prep for the approach; transferred controls; did a quick brief; and switched controls back. I think I called for the in-range; but we were now less than 5 miles from the final approach fix and were given more vectors and a frequency change to tower. Now I began configuring for the approach as tower asked us to keep our speed up to the marker. Unfamiliar with [runway] 19R; I spent a little time reviewing the distance to the runway and altitude of the FAF to figure out what a safe speed to the marker would be since I know that we have a lot of configuration issues with iad approaches. Once we were completely configured; I called for the 'before landing' checklist and we must have skipped the in-range checklist; because the flight attendant called us once we were stopped on the taxiway and informed us that the seatbelt sign was still off. I've been told that we are trying to stop doing the gibbz; I think that's a great way to reduce distractions during the arrival phase into a busy airport.
Original NASA ASRS Text
Title: Air Carrier Captain reports forgetting to turn on the seatbelt sign prior to landing at IAD due to the extremely busy arrival and approach phase. Vectors to avoid VFR traffic and the GIBBZ arrival were cited as the major distractors.
Narrative: The GIBBZ arrival is a very busy arrival and it was even busier than usual that day. I got distracted both by the approach and the added distractions of two close encounters with VFR traffic and many turns and descents from ATC at a busy time of the arrival. We landed with the seat belt sign off. Passing through FL180 we were distracted by the busy GIBBZ arrival. Just as we were passing through 10;000; where I would usually check the seatbelt sign; we were given our runway assignment and it was not what we had expected (we were given [Runway] 19R) and we were given what sounded like an urgent traffic alert with a turn off the arrival to avoid VFR traffic. We also had to call the Flight Attendant; because we didn't have a sterile light. Then; as we were trying to prepare for the approach to Runway 19R we were given another turn back towards the airport; then a frequency change. On checking in we were given another traffic alert of a VFR target less than 2 miles and 500 FT above our assigned altitude. We picked up this traffic visually just as the resolution advisory was being enunciated. We called and kept the traffic in sight visually until we were clear of conflict; then finished the prep for the approach; transferred controls; did a quick brief; and switched controls back. I think I called for the in-range; but we were now less than 5 miles from the final approach fix and were given more vectors and a frequency change to Tower. Now I began configuring for the approach as Tower asked us to keep our speed up to the marker. Unfamiliar with [Runway] 19R; I spent a little time reviewing the distance to the runway and altitude of the FAF to figure out what a safe speed to the marker would be since I know that we have a lot of configuration issues with IAD approaches. Once we were completely configured; I called for the 'Before Landing' Checklist and we must have skipped the In-Range Checklist; because the Flight Attendant called us once we were stopped on the taxiway and informed us that the seatbelt sign was still off. I've been told that we are trying to stop doing the GIBBZ; I think that's a great way to reduce distractions during the arrival phase into a busy airport.
Data retrieved from NASA's ASRS site 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.