elihoole/asrs-aviation-reports huggingface dataset:
Date: 201205
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: MU-300 Diamond 1/1A
Operator: Corporate
Operating under: Part 91
Flight plan: VFR
Mission: Ferry / Re-Positioning
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Normal Brake System
Component problem: Failed
Reporter organization: Corporate
Reporter function: First Officer; Pilot Flying; Trainee
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After routine landing on Runway 11 I informed the Captain immediately; that I had no braking action.  The Captain assumed aircraft control and attempted braking from his side with the same result.  He then switched off the anti-skid and reattempted braking.  Still no brakes.  Captain then reached for the emergency brakes lever and was able to bring the aircraft to a complete stop on the runway.  Both main gear tire's were flat at the end of landing rollout.  Captain secured a tug and the aircraft was relocated to the hanger.


Second narrative: After landing the First Officer informed me that he had no braking action.  I told the First Officer that I had the aircraft and tried to apply brakes on my side.  I did not have braking action either.  I then began to apply the emergency brakes and brought the aircraft to a stop on the runway.  The tires on the aircraft went flat.  We secured a tug and dollies for the wheels and removed the aircraft from the runway.


Synopsis: An MU300 had normal brake failure during landing when the First Officer applied the brakes.  The Captain's brakes are also inoperative and the aircraft was brought to a stop using the emergency brakes resulting in two flat tires.
Date: 201212
Local time of day: 1801-2400
Location: SBY.Airport, MD
Light: Night
Aircraft: Dash 8 Series Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class D SBY
ATC / advisory: Tower SBY
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On the arrival into SBY we were cleared for the visual approach Runway 14. During the visual approach for Runway 14 the PF descended on a left base entry too low. The EGPWS system went off at 560 FT. At the sign of the EGPWS alert the PF then increased the pitch of the plane to regain a safe altitude [which led to] a stabilized approach into Runway 14. Both pilots were looking outside during the visual approach. PM should stay inside during a visual approach especially at night.




Synopsis: Dash 8 First Officer reported EGPWS alert was triggered on night visual approach to SBY.
Date: 201406
Local time of day: 1201-1800
Location: ATL.Airport, GA
Flight conditions: VMC
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Landing
Airspace: Class B ATL
ATC / advisory: Tower ATL
Second aircraft: B757 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: We were on a visual approach to [Runway] 27L Atlanta following another carrier's B757. We were approximately three miles in trail on the TCAS display. At approximately 100 FT; we encountered wake turbulence from the B757. It was the Captain's leg and he initiated a go-around. We coordinated with Atlanta Tower and Atlanta Approach to sequence back in for another approach. I told the Approach Controller the separation between us and the B757 was too tight and he stated; 'It is our new separation rules.' We landed uneventfully after the second approach. The new rules for separation used by Atlanta Approach are too tight. If they continue to bring aircraft in with minimal separation; there will be more of these events.




Synopsis: B737-800 Firrst Officer reported encountering wake turbulence on approach to ATL in trail of B757 that resulted in a go-around. Reporter cited new minimal ATC separation techniques as causal.
Date: 201812
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B777-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Chart Or Publication; Incorrect / Not Installed / Unavailable Part
Primary problem: Procedure

Narrative: Planning for a Runway XXL departure; we received clearance from Ground control to push our aircraft; a B777-300; out of ZXX ramp on to Taxiway XX; with aircraft tail pointed east; aircraft tug disconnect abeam Terminal XX. After push and engine start was completed; we called for taxi clearance. Ground control cleared us to taxi to Runway XXL via ZXX intersection; transitioning westbound on Taxiway XY; then to hold short of ZXY intersection. We replied we were unable comply as this was contradictory to notes in taxi charts which states: 'B767-300 aircraft and greater holding on taxi lane X abeam Taxiway Terminal XX are not authorized to make the left turn on Taxiway ZXX under power' The Controller replied that turns on to ZXX with westbound Taxi on XY are authorized. He continued that hard turns on to ZXX with east taxi are NOT authorized. He added that this issue had been discussed prior with [Company]; and that in this circumstance we were to make a 'slight' left turn on to ZXX followed by the right turn onto XY. I interpreted this as to not follow the taxi lines; as our jet blast could cause damage. With some reluctance we complied with Controllers' directive; except for following the taxi lines as painted. Utilizing minimal power; we turned onto ZXX; followed by right turn on to XY and continued the taxi to Runway XXL. Obviously this was a confusing situation. The Controllers' directive should mirror FAA approved charts. Creating ones' own taxi path might sometimes be acceptable for smaller aircraft; but not for larger aircraft such as 777-300. It increases the potential for a surface incident.




Synopsis: B777 Captain reported ATC issued taxi clearance contrary to chart taxi procedures.
Date: 201909
Location: ZZZ.ARTCC, US
Aircraft: Commercial Fixed Wing
Operator: Air Taxi
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZZZ
Aircraft component: VHF
Component problem: Failed; Malfunctioning
Reporter organization: Air Carrier
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Air Traffic Control Issued New Clearance; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Equipment / Tooling
Primary problem: Aircraft

Narrative: Instructed ZZZ via CPDLC to contact ZZZ1 Center south of [landmark]. Attempted contact; no response. Thinking out of contact range CPDLC control cancelled by ZZZ Oceanic. Made several attempts on #1 Com radio with no response. Tried #2 Com with no contact. At this time; #1 com displayed FAIL in Active and Standby Displays. With no response on #2 Com plus a FAIL message on #1 Com; set 7600 on transponder. At this time; #2 Com frequencies could be set; but could [not] transmit. We could [hear] Center's instructions and confirm instructions with ident; but eventually #2 Com displayed FAIL in both windows. Through this; we received intermittent descent clearances to descend towards destination; but this was intermittent because frequencies could not be set on Com #2. At this point; initiated SAT phone contact with any center we contact. After numerous attempts; eventually made contact with ZZZ2 Approach and vectored via vectors through the phone for ILS XXR to uneventful landing. Taxied via light gun signals from the Tower and followed vehicle to assigned gate. Contacted Tower regarding reports that needed to be filled and [they] indicated none were needed. Please note that this event started at TOD (Top of Descent) to landing.




Synopsis: Pilot reported loss of both VHF communications systems during flight.
Date: 201910
Local time of day: 0601-1200
Location: PHL.Airport, PA
Flight conditions: VMC
Light: Daylight
Aircraft: Citation V/Ultra/Encore (C560)
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B PHL
ATC / advisory: TRACON PHL
Second aircraft: B737 Next Generation Undifferentiated
Reporter organization: Air Taxi
Reporter function: Other / Unknown
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Inflight Event / Encounter Wake Vortex Encounter; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: During vectors for approach; crew was advised they were 7 nm in trail of a B737. Prior to the FAF; encountered a sharp roll left; followed by roll right to a 90 degree angle.  Altitude loss was less than 300 feet. Crew recovered aircraft to assigned altitude; advised ATC of severe turbulence encounter; and continued a normal approach to landing. Subsequent inspection by Maintenance determined no airframe damage.




Synopsis: CE560 pilot reported a 90-degree roll resulted after encountering wake turbulence from preceding B737 on approach to PHL.
Date: 201311
Local time of day: 1201-1800
Location: PHL.Airport, PA
Flight conditions: VMC
Light: Night
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp PHL
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Flight Engineer
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We had passed Taxiway R and were short of Taxiway T when the Captain set the parking brake. We wished to verify the taxi instruction with ramp; but the ramp frequency was congested. While we waited to talk to the Ramp Controller; an MD-80 cleared Runway 27R onto Taxiway T and then left towards Taxiway TA. The MD-80's right wingtip cleared our aircraft's nose by no more than a few yards. Since we were parked on Taxiway K between Taxiways R and T; the distance for the MD-80 to visibly clear our aircraft was in question. We proceeded to our assigned gate after an aircraft cleared the alleyway.




Synopsis: B757 First Officer reported an MD-80 clearing a runway just missed his wingtip as he taxied by.
Date: 201809
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Mission: Training
Flight phase: Landing
Aircraft component: Main Gear
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On rollout from landing; the student and I experienced directional control difficulties that led to the airplane exiting Runway 21 on the south side by a few feet. We stopped the airplane and shutdown to inspect the possible damage. The top of the torque link on the left main gear had come apart from its attachment resulting in a counterclockwise twisting of the left main landing gear that caused the airplane to lose control on rollout and yaw to the left. No side loading or unsafe touchdown occurred during the touchdown prior to the incident. Future preflights will consist of examining the torque link attachments with greater scrutiny.




Synopsis: PA-28 flight instructor reported a loss of control and runway excursion after landing due to left main gear torque link issue.
Date: 201701
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: J3 Cub
Operator: Personal
Operating under: Part 91
Flight plan: None
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Departed ZZZ for local flight. During flight; 7 miles west of ZZZ and at 6;500 MSL; began to lose engine power. Attempted to return to airport; at approximately 1.5 miles from airport engine stopped and was forced to turn back to a less developed area and land. On landing; struck a dirt berm and the gear was damaged.




Synopsis: Piper J-3 Cub pilot reported the aircraft lost power during climbout and was forced to make an emergency landing. The landing gear was damaged when the aircraft hit a dirt berm after landing off field.
Date: 201703
Local time of day: 1801-2400
Location: ZDC.ARTCC, VA
Flight conditions: IMC
Weather elements / visibility: Rain
Light: Night
Aircraft: Small Transport; Low Wing; 2 Turboprop Eng
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZDC
ATC / advisory: Center ZDC
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Situational Awareness; Human-Machine Interface
Second reporter function: Single Pilot
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Aircraft X was enroute to EQY. A crossing restriction of 30 miles NE of GSO was issued and an automated handoff to GSO approach was initiated and accepted. The aircraft was then instructed to contact GSO approach. At approximately [time removed] the aircraft called back and reported a total engine failure and was descending. He then requested the closest airport. The aircraft was given 2 airports; DAN 15 miles to his east and GSO 40 miles to his south. The PIC reported he couldn't make GSO and needed the closest airport. I gave him an initial vector to DAN; 15 miles to his east. The PIC requested runway length which was provided as well as the frequency for the runway lights. Several airport position reports were issued. As the aircraft descended radio communications became broken and some information was relayed through other aircraft on the frequency to Aircraft X. The aircraft was observed to turn and get lined up for Runway 20 at DAN. The radar target and altitude information was observed to approximately 100 AGL. The PIC called the departure airport and reported a safe landing approximately 12 minutes later.


Second narrative: Experienced dual engine failures while in IMC with heavy rain approximately 50 miles north of Greensboro; NC and descending per clearance to 13;000 feet. The right engine failed then the left engine over a 1-2 minute timeframe. I stabilized the aircraft and [advised ATC]. Washington Center advised of an airport located approximately 12 NM east of my present position. I landed at DAN without incident. No damage or injury to myself; my passenger; airport property; or aircraft.


Synopsis: ZDC Controller and the pilot involved reported that the aircraft lost both engines and landed successfully at a nearby airport.
Date: 201605
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Dawn
Aircraft: Citation V/Ultra/Encore (C560)
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Air Taxi
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Communication Breakdown; Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Airport
Primary problem: Human Factors

Narrative: We stated our taxi intentions over CTAF. Taxied from [the FBO] to the runway. We received a reply 'Runway clear; no known traffic; altimeter setting. Have a nice flight' we continued to monitor CTAF. We stopped to complete line-up checklist for about a minute and made our takeoff announcement over CTAF to which there was no reply from anyone. We took the runway and followed normal takeoff procedures. Visually watching down the runway we did not see anyone. After rotation and about 450 ft AGL we saw a truck driving down the runway below us. We called out to the vehicle who responded he did not receive any of our previous transmissions.


Second narrative: [Report narrative contained no additional information.]


Synopsis: Cessna 560 flight crew reported departing an uncontrolled field in low light; dawn conditions; and had a close encounter with a vehicle on the runway.
Date: 201708
Local time of day: 1201-1800
Location: BOS.Airport, MA
Flight conditions: IMC
Light: Daylight
Aircraft: Medium Transport
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B BOS
ATC / advisory: TRACON A90
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The event took place on the OOSHN4 arrival into BOS just after crossing the FLUTI fix while in communications with Boston Approach Control. The autopilot was engaged. Before reaching the initial arrival fix OOSHN; ATC issued the clearance to decent via the OOSHN4 arrival. Upon crossing FLUTI with the VNAV armed the plane began to decent below 9;000 feet to cross GGABE at 6;000 feet. Just below 9;000 feet ATC issued a right turn to a heading of 280 and decent to 6;000 feet. The crew complied with instructions and placed the airplanes navigation panel in 'heading mode;' then commanded the turn to a heading of 280 while continuing the decent to 6;000 feet. At 7;500 feet ATC called us and told us the altitude assigned was 9;000 feet. ATC then issued a second clearance to a heading of 320 descent 6;000 feet. All ATC instructions were repeated back to ATC when received.ATC repeatedly called us [the wrong call sign; X;] and had to correct himself many times during the course of this event. There was many other aircraft communication during this event including a call sign of X referring to another aircraft. It is my belief that the ATC controller became task saturated and lost his situational awareness. In doing so; his communications to several airplanes including ours became confusing. Both pilots involved in this event agreed that they heard the same instructions. The ATC controller was removed from the radio and another controller continued issuing clearances. We were vectored during the remaining of the approach until cleared for the ILS 4R into BOS. We landed without further incident.


Second narrative: [Report narrative contained no additional information.]


Synopsis: Corporate Jet flight crew reported receiving conflicting ATC instructions on the OOSHN4 arrival into BOS.