 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air taxi captain reported initially lining up on the wrong runway following distractions related to local traffic and bird activity.
| Attributes | |
| ACN | 1615753 |
| Time | |
| Date | 201902 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | PBI.Airport |
| State Reference | FL |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 135 |
| Flight Phase | Final Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Lined up on wrong runway at vrb on visual approach. Weather was day VFR. Initial weather indicated runway 4 landing. Crew briefed and executed appropriate checklists. New weather caused change in runway. First officer (first officer) set FMS and set approach for runway 12. Due to high volumes of local training traffic and parachuting I did not catch him hitting the actual load function. I was distracted. Several birds were also observed with more distraction. We were cleared for visual to runway 12. I asked [for] vectors to final to be executed. The first officer did as requested; however [runway] 04 approach popped up. In the heat of battle and distractions at hand we missed the [runway] 12 approach. ATC had already cleared us for a visual [but] we did not catch the fact that [runway] 4 was in sequence. We began VFR visual sequencing for wrong approach following FMS data. ATC queried us as would be expected. We asked for sequencing back around for [runway] 12 [and] we landed without incident. More diligence when setting up approach sequence. Cross check and confirm each hand movement of buttons. Divide time better with oncoming approach.
Original NASA ASRS Text
Title: Air taxi Captain reported initially lining up on the wrong runway following distractions related to local traffic and bird activity.
Narrative: Lined up on wrong runway at VRB on visual approach. Weather was day VFR. Initial weather indicated runway 4 landing. Crew briefed and executed appropriate checklists. New weather caused change in runway. FO (First Officer) set FMS and set approach for runway 12. Due to high volumes of local training traffic and parachuting I did not catch him hitting the actual load function. I was distracted. Several birds were also observed with more distraction. We were cleared for visual to runway 12. I asked [for] vectors to final to be executed. The FO did as requested; however [runway] 04 approach popped up. In the heat of battle and distractions at hand we missed the [runway] 12 approach. ATC had already cleared us for a visual [but] we did not catch the fact that [runway] 4 was in sequence. We began VFR visual sequencing for wrong approach following FMS data. ATC queried us as would be expected. We asked for sequencing back around for [runway] 12 [and] we landed without incident. More diligence when setting up approach sequence. Cross check and confirm each hand movement of buttons. Divide time better with oncoming approach.
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.