Date: 201304
Local time of day: 1801-2400
Location: DAL.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Taxi
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Final Approach
Airspace: Class C DAL
ATC / advisory: Tower DAL
Second aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Air Taxi
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Human-Machine Interface; Communication Breakdown; Confusion; Training / Qualification
Second reporter function: First Officer; Pilot Flying
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft RA
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Procedure; Environment - Non Weather Related
Primary problem: Procedure

Narrative: A TFR had just been lifted with multiple aircraft holding and inbound to the airport. Numerous runway changes were being issued to various aircraft; including ours; by Approach Control. After our runway change from 13R to 13L and being cleared for a visual approach by Approach Control and cleared to land on Runway 13L by Tower; 'ILS 13L OTS' as stated by the ATIS; we were beginning the process of configuring for landing. Initial flaps and landing gear had just been extended and we were about to configure to landing flaps around the FAF. At that time; with no previous 'TRAFFIC' warning; we got a completely unexpected RA with the voice prompt 'DESCEND NOW' and the VSI presentation of a descent. The SIC (PF) disconnected the AP and started a slow descent while we looked for traffic and tried to gain situational awareness. A few seconds after the onset of the RA and with no visual contact with traffic; the PIC commanded; 'follow the RA now!' This was done by the SIC. However the conflicting traffic continued a descent matching our descent rate and the RA continued with no further voice prompt but with a visual display commanding a descent on the VSI. This continued until the SIC became concerned about the RA possibly leading to a low altitude and a CFIT issue. About this time the PIC gained visual contact with another aircraft above and behind our position on the parallel visual to Runway 13R. It was obvious that this was the traffic causing the event and it was on a normal visual to the parallel runway and was no threat. About that time the RA went away with no voice prompt. A stabilized approach was continued to landing. No report was made to ATC because no deviation from ATC clearance was experienced and no intrusion by the other aircraft was experienced and there was no failure with ATC. Whether the other aircraft experienced an RA or had visual contact with us is unknown. This is believed by the crew to be a nuisance RA. Regarding human factors: The unexpected TCAS RA; with no earlier warning and in an unusual area of flight operations for a TCAS event; and under high workloads; was initially thought by both pilots to be an anomaly or malfunction. However in the case of no other evidence of a malfunction; the RA was followed to the extent as not to jeopardize the aircraft further by entering into a GPWS or CFIT event. This presents a dual-minded pilot. That is; the innate desire not to descend in close proximity to the ground or below a normal glidepath and the desire to descend via the RA as is regularly instilled in the pilot during simulator and classroom instruction. The delay in this decision making process can exceed the time allotted to execute the RA action with success. In addition; the belief; due to frequency of the event; that the RA is not 'real' and is generated by another aircraft on the other parallel visual approach leads the pilots to complacency in the event of an RA in this situation; when in fact the RA may not be a nuisance RA and is in fact a potential collision event. This complacency can also lead to the pilots not reacting in time to successfully resolve a real collision possibility. The tendency of the pilot after discovering the RA event was a 'nuisance RA' is to not report the event to ATC because no party was really responsible for the event 'trigger;' and in this event; no deviation from ATC clearance was experienced by either aircraft.


Second narrative: [Narrative contains no additional information.]


Synopsis: An air carrier flight crew at 2;000 feet on a visual approach to DAL Runway 13L followed a TCAS RA command from an unannounced aircraft on approach to 13R.