37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1685701 |
Time | |
Date | 201908 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | LAS.Airport |
State Reference | NV |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Ground Event / Encounter Other / Unknown |
Narrative:
We received clearance to taxi to 8L from [FBO] via F (H?). It is important to note it was dark; and approaching 8L the taxi lines and lighting became increasingly difficult to see/interpret although I was familiar yet annoyed at the lack of proper depiction. We were cleared into position. While I was occupied accomplishing the takeoff checklist; the PIC indicated his dissatisfaction with the taxi line clarity. I looked up and pointed out we had just passed the turn to enter 8L. He made the correction immediately without impacting 1L; which in the process of the correction the controller advised us of the potential; I replied we had mitigated. We positioned on 8L as instructed; and confirmed 8L correct. When; as in this case; the runway numbers are not visible per our instructions; I use the mfd at 250 feet setting to confirm our position and alignment with the runway as assigned. In fact I use this as a double check for each takeoff in addition to the SOP requirement. We were cleared for takeoff. At this point my job as pm [pilot monitoring] is to stay inside and monitor speeds; engine instruments and such. At V1 I noticed a taxiway alert but per SOP had already called V1. Nothing indicated the aircraft was un-flyable so I called rotate. No unusual sound; just what seemed like a false alert. Nothing unusual whatever was noted for remainder of the evening. The PIC did not fail to post flight; made note of nothing to myself; and my post flight found nothing. I do look for obvious damage in all cases but found none apparent. I had mulled asking this be written up; as the following day in las got a similar alert (different runway) upon takeoff; but my suspicion; if memory serves; was a deferred database issue. In any case wrong runway/taxiway alert are not uncommon at las which can be testified by any aircraft X pilot who has loaded the RNAV approach to 19R for backup and flew it visually per ATC instructions. You will get it every time. The 8L/1L area is a known problem area. At night it is poorly marked; taxi lines are difficult to see; and adequate lighting is nonexistent. Green taxiway centerline lights are an absolute must; especially; again; as this is a known; published problem area. Rclm [runway center line markings] are a must. It is inconceivable to not have this at night; especially as the runway numbers are 1000' down the runway. Night takeoffs from this runway should be prohibited until this is rectified.
Original NASA ASRS Text
Title: Corporate First Officer reported issues with lighting; markings; and no runway identification for 8L/1L at LAS airport.
Narrative: We received clearance to taxi to 8L from [FBO] via F (H?). It is important to note it was dark; and approaching 8L the taxi lines and lighting became increasingly difficult to see/interpret although I was familiar yet annoyed at the lack of proper depiction. We were cleared into position. While I was occupied accomplishing the takeoff checklist; the PIC indicated his dissatisfaction with the taxi line clarity. I looked up and pointed out we had just passed the turn to enter 8L. He made the correction immediately without impacting 1L; which in the process of the correction the controller advised us of the potential; I replied we had mitigated. We positioned on 8L as instructed; and confirmed 8L correct. When; as in this case; the runway numbers are not visible per our instructions; I use the MFD at 250 feet setting to confirm our position and alignment with the runway as assigned. In fact I use this as a double check for each takeoff in addition to the SOP requirement. We were cleared for takeoff. At this point my job as PM [Pilot Monitoring] is to stay inside and monitor speeds; engine instruments and such. At V1 I noticed a taxiway alert but per SOP had already called V1. Nothing indicated the aircraft was un-flyable so I called rotate. No unusual sound; just what seemed like a false alert. Nothing unusual whatever was noted for remainder of the evening. The PIC did not fail to post flight; made note of nothing to myself; and my post flight found nothing. I do look for obvious damage in all cases but found none apparent. I had mulled asking this be written up; as the following day in LAS got a similar alert (different runway) upon takeoff; but my suspicion; if memory serves; was a deferred database issue. In any case wrong runway/taxiway alert are not uncommon at LAS which can be testified by any Aircraft X pilot who has loaded the RNAV approach to 19R for backup and flew it visually per ATC instructions. You will get it every time. The 8L/1L area is a known problem area. At night it is poorly marked; taxi lines are difficult to see; and adequate lighting is nonexistent. Green taxiway centerline lights are an absolute must; especially; again; as this is a known; published problem area. RCLM [Runway Center line Markings] are a must. It is inconceivable to not have this at night; especially as the runway numbers are 1000' down the runway. Night takeoffs from this runway should be prohibited until this is rectified.
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.