ASN Wikibase Occurrence # 297345
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Wednesday 1 May 2002 |
| Time: | 15:53 LT |
| Type: |  Beechcraft 400A Beechjet |
| Owner/operator: | Flight Options, Inc. |
| Registration: | N498CW |
| MSN: | RK-108 |
| Year of manufacture: | 1995 |
| Total airframe hrs: | 2410 hours |
| Engine model: | Pratt & Whitney JT15D-5 |
| Fatalities: | Fatalities: 0 / Occupants: 6 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Baltimore, Maryland -
 United States of America
|
| Phase: | Unknown |
| Nature: | Executive |
| Departure airport: | Reading Regional Airport/Spaatz Field, PA (RDG/KRDG) |
| Baltimore/Washington International Thurgood Marshall Airport, MD (BWI/KBWI) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
While on a visual approach, the captain had difficulty with the flight management system. He and the first officer exchanged words about it, and argued as to whether they were cleared for the approach. During that timeframe, with the airplane about 5 miles from the airport, 238 knots and 3,000 feet, the controller also asked the crew if they were "going to be able to get down, " to which the first officer responded, "ah, we're looking." About 30 seconds later, the first officer confirmed that the airport was in sight, and, "we'll be able to get down." After switching over to the tower frequency, the airplane was cleared to land, and about 20 seconds later, the first officer asked the captain, "You gonna be able to make it?" The captain did not respond, but 20 seconds later asked about the runway length, which the first officer gave him. The first officer then told the captain that the airplane was Vref plus forty, and twice said, "There's no way." He then said twice, "Go around." The airplane crossed the landing threshold about 150 feet agl, 166 knots, and the captain landed. The airplane subsequently overran the end of the runway, and went through some lights and antennas. A review of company standard operating procedures revealed that the crew missed numerous required callouts and checklist items, that the captain was trying to program the FMS when the first officer should have been doing it, that the captain should have initiated a go-around when advised that the airplane was not within the "visual approach window," and that after the captain did not respond to the first officer's calls, the first officer should have announced that he was assuming control, and "taken the necessary actions to return the aircraft to a safe flight condition."
Probable Cause: The captain's failure to go around. Factors included the captain's preoccupation with the flight management system, the crew's failure to adhere to company standard operating procedures, and the lack of proper crew coordination.
Accident investigation:
 |
|
Sources:
NTSB IAD02FA047
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 14-Oct-2022 17:27 | ASN Update Bot | Added |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation