Narrative:

As we approached 4S; we contacted ground control on 121.7. They instructed us to taxi to runway 36R via south. As we taxied south on south; we ran the runway 36R; taxi checklist. Upon passing S4; I switched to the assigned tower frequency for runway 36R. About that same time the captain and I noticed that the south end of taxiway south passed S3 was blocked off and construction was occurring. Due to it being blocked off; we turned at T3 and informed tower we were ready to go at T3. Upon running the numbers on acar's we found we could not get numbers for 36R/T3 and requested full length. We then explained to the controller that the south end of the taxiway was closed and we did not have numbers for a T3 departure which required the back taxi. The controller then stated that he was not aware of any construction occurring at the south end of the taxiway. We back taxied full length and departed without any further incident. During the back taxi we did note various barricades which appeared to be in the run up area south of T3; but we could not verify this. Upon a review of the NOTAMS; we did not find any related NOTAMS to the closure. However; upon review of the FAA web site there are two NOTAM's cvg 08/119 cvg twy south south 200 clsd & cvg 08/118 cvg twy T clsd south twy T3. Identification; while there was no specific incursion that occurred; it was determined that something was wrong when we encountered the barricades and were informed by tower that they were not aware of the closures. That was the point that we realized that an issue had arisen. Cause; three issues caused this event. 1. The taxi instructions did not include anything about us needing to use T3 as the entrance to the runway. 2. The NOTAM's in the packet did not give any indication as to the closures. 3. The tower controller not being aware of the construction closing the south end. All three items contributed. Response; once we realized that something was wrong; we informed tower of the closure first. Then upon running new numbers; we found we could not depart from that intersection. As such we requested the short back taxi to allow us to use the take off data we had obtained. Once everyone; tower and aircraft crew were on the same page; a normal departure occurred. Suggestions; verification of all NOTAM's being placed in the briefing packet is crucial. We can only use the information that we are provided with. Both the captain and I reviewed the packet a second time once airborne and could not locate the NOTAM's. It is entirely possible that both crew members missed the NOTAM's; a section did not print; any number of possibilities; but care must be taken by all persons from the flight crew to operations to make sure that all NOTAM's are found and reported.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air Carrier departing CVG described a confused take off event when taxiway closures were not know to ATC; not located in NOTAM information and incomplete taxi instructions.

Narrative: As we approached 4S; we contacted ground control on 121.7. They instructed us to taxi to Runway 36R via S. As we taxied South on S; we ran the Runway 36R; taxi checklist. Upon passing S4; I switched to the assigned tower frequency for Runway 36R. About that same time the Captain and I noticed that the South end of Taxiway S passed S3 was blocked off and construction was occurring. Due to it being blocked off; we turned at T3 and informed tower we were ready to go at T3. Upon running the numbers on ACAR's we found we could not get numbers for 36R/T3 and requested full length. We then explained to the controller that the South end of the taxiway was closed and we did not have numbers for a T3 departure which required the back taxi. The controller then stated that he was not aware of any construction occurring at the South end of the taxiway. We back taxied full length and departed without any further incident. During the back taxi we did note various barricades which appeared to be in the run up area South of T3; but we could not verify this. Upon a review of the NOTAMS; we did not find any related NOTAMS to the closure. However; upon review of the FAA web site there are two NOTAM's CVG 08/119 CVG TWY S SOUTH 200 CLSD & CVG 08/118 CVG TWY T CLSD SOUTH TWY T3. Identification; while there was no specific incursion that occurred; it was determined that something was wrong when we encountered the barricades and were informed by tower that they were not aware of the closures. That was the point that we realized that an issue had arisen. Cause; three issues caused this event. 1. The taxi instructions did not include anything about us needing to use T3 as the entrance to the Runway. 2. The NOTAM's in the packet did not give any indication as to the closures. 3. The tower controller not being aware of the construction closing the South end. All three items contributed. Response; once we realized that something was wrong; we informed tower of the closure first. Then upon running new numbers; we found we could not depart from that intersection. As such we requested the short back taxi to allow us to use the take off data we had obtained. Once everyone; tower and aircraft crew were on the same page; a normal departure occurred. Suggestions; verification of all NOTAM's being placed in the briefing packet is crucial. We can only use the information that we are provided with. Both the captain and I reviewed the packet a second time once airborne and could not locate the NOTAM's. It is entirely possible that both crew members missed the NOTAM's; a section did not print; any number of possibilities; but care must be taken by all persons from the flight crew to operations to make sure that all NOTAM's are found and reported.

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.