elihoole/asrs-aviation-reports huggingface dataset:
Date: 202201
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Initial Approach
Second aircraft: Light Sport Aircraft
Reporter organization: Personal
Reporter function: Pilot Flying; Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Instrument
Human factors: Workload; Distraction
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft Y; a gyrocopter in the pattern at ZZZ utilized lower altitude to take advantage of right of way rules cutting off 2 aircraft in the pattern. Aircraft Y made a crosswind call in front of other traffic on the departure leg. During final approach in the pattern Aircraft Y laterally displaced themself right of the centerline; and proceeded back across the centerline in front of my aircraft causing a near mid air collision.




Synopsis: Pilot in the VFR pattern at a non towered airport reported a NMAC with a gyrocopter.
Date: 202003
Local time of day: 0601-1200
Location: PHL.TRACON, PA
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B PHL
ATC / advisory: TRACON PHL
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Conflict Airborne Conflict
Detector: Automation Aircraft RA
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Traffic resolution advisory warning system alert (TA/RA) at 3;500 ft. about 5 miles from COWAD intersection on ILS localizer Runway 17. [Cause was] VFR traffic at 3;000 ft. in Runway 17 approach corridor to PHL. [We] complied with RA to climb from 3;500 ft. [Recommend] ATC [provide] communication advisory away from traffic.




Synopsis: EMB-145 First Officer reported responding to a TCAS RA on approach to PHL to avoid VFR traffic in the approach corridor.
Date: 201601
Local time of day: 1801-2400
Location: LAX.Airport, CA
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Initial Approach
Airspace: Class B SCT
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Workload
Anomaly: ATC Issue All Types; Deviation - Speed All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Human Factors; Aircraft
Primary problem: Human Factors

Narrative: Cleared to descend via the Seavu2 Arrival; Cleared ILS to runway 24R. Speeds assigned (up and down) from 250 to 180 knots. Approach clearance cancelled. Descend to 2;600 feet; maintain 190 knots until glide slope; cleared to intercept the glideslope from that altitude.Due to higher speeds and late clearance for the approach; horizontal mode left in 'NAV.' FMS NAV was verified as coinciding with localizer (note: not cleared to intercept the localizer). Once cleared the approach; the FMA initially indicated localizer capture; but subsequently reverted to heading with no pilot input. Without the localizer capture; the glideslope did not capture. I disconnected autopilot which resulted in a slight climb above assigned altitude (<300 feet). Repeated attempts to arm the approach failed so manual control to intercept and track the localizer and glideslope without flight director guidance. High speed until approaching glideslope along with failure of localizer and glideslope capture resulted in higher than normal rate of descent. Approaching 1;200 feet acquired runway 24R visually. Approaching 1;000 feet Pilot Monitoring announced high airspeed but we continued approach due to VMC conditions and achieved stable criteria by 500 feet.




Synopsis: On the approach to LAX; the First Officer was high and fast; but was stable by 500 feet.
Date: 201712
Local time of day: 0601-1200
Location: EGTT.ARTCC, FO
Light: Daylight
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: Center EGTT
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General Physical Injury / Incapacitation
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Approaching FL320 in the climb; clear; smooth with seat belt sign off. Experienced probable wake turbulence for approximately 5 seconds. Smooth air immediately before and after event. No airplanes in close proximity that we saw. Called purser; she reported all ok. Later the purser reported that 3 flight attendants were reporting minor injuries; but were able to perform their duties. All were able to complete the flight while performing all normal duties.


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


Synopsis: B777 flight crew reported three Flight Attendants were slightly injured in a wake turbulence encounter at FL320 near TNT VOR in England.
Date: 201309
Local time of day: 1801-2400
Location: GYY.Airport, IN
Flight conditions: VMC
Light: Night
Aircraft: Challenger 605
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Flight phase: Landing
Airspace: Class D GYY
ATC / advisory: Tower GYY
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness; Confusion
Anomaly: Other unwanted situation
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: We were cleared for a visual approach about 7 miles from Runway 12 and on a modified right base leg. Turning about a 3 mile final and descending with landing lights on. We were cleared for and made a normal landing. However; we both noticed that on the extended runway centerline where new pavement is being added; there were reflective cones that were lined and shining white with reflective tape that was being illuminated by the landing lights. This could create a hazard if the PAPI wasn't being followed or was OTS; especially since the elevated burm for the train track is still in place between the new concrete and existing runway. The cones were lined up to make it look almost like landing lights. They could possibly be removed/moved or replaced with cones not using reflective tape. Possibly a set of white closed lights on that portion of the construction would help. Notice of this could also be placed on the ATIS and NOTAM'd to be cautious of the false extended centerline and to fly the PAPI.

Callback: The reporter had not been back and was unable to comment on the current status.



Synopsis: A CL-600 Captain advised that a row of reflective safety cones identifying new pavement adding to the extended Runway 12 centerline reflect landing lights at night and could be mistaken for useable runway.
Date: 201405
Local time of day: 1801-2400
Location: N90.TRACON, NY
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Descent
ATC / advisory: TRACON N90
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Communication Breakdown; Confusion
Anomaly: Conflict NMAC
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; ATC Equipment / Nav Facility / Buildings; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: The training flight was conducted under 'Radar Services'; where the original frequency was only working between the altitudes of 3;500 and 4;000 FT. During the descent; tried many times to get a hold of the NY TRACON on 120.15; trying to cancel flight following. While descending between 3;800-3;500 FT the radio reception got weaker; and tried to go back to 4;000 feet to make a last attempt to cancel radar services; as we were reaching 3;800 FT; on the radio; heard someone say to stop descent at for traffic; followed a few seconds later [by an aircraft] flying overhead. Right away we rapidly descended to 2;500 FT to clear any possible conflict and stay clear of Class 'B' ahead; as the approach continued; tried different frequencies; with no luck. Once on the ground; call NY TRACON via the phone line to inform them we were safe on the ground; and due to radio coverage and volume; it was impossible to cancel in the air.




Synopsis: C172 instructor reports difficulty canceling flight following with NY TRACON during descent due to a weak radio or lack of VHF coverage. Climbing to regain VHF contact results in a NMAC. Flight following is canceled on the ground.
Date: 201209
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: MD-82
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Valve/Oil System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Training / Qualification; Troubleshooting
Second reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; Flight Crew Diverted; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At FL320 the right Oil Strainer Clog light illuminated. The QRH procedure was performed. The light never extinguished. The oil pressure and quantity dropped below normal. Right engine was secured per the QRH. [We] landed over weight at 134;000 LBS without incident.


Second narrative: [Narrative 2 contained no additional information.]


Synopsis: An MD-82 Oil Strainer Clog light illuminated then would not extinguish as oil pressure and quantity decreased so following the QRH the engine was shutdown and the flight diverted to an enroute.
Date: 201412
Local time of day: 0601-1200
Location: SJC.Airport, CA
Light: Daylight
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower SJC
Second aircraft: Small Transport
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Procedure; Human Factors; Aircraft
Primary problem: Procedure

Narrative: I cleared Aircraft X to land on runway 12R. NCT vectored Aircraft Y behind Aircraft X and applied visual separation correctly. As Aircraft Y was flying faster than Aircraft X; the NCT controller called me and asked if I would move Aircraft X to runway 12L. I told him that I would do so. I instructed Aircraft X to change to runway 12L and cleared him to land. The pilot replied 'Unable'. I cleared him to land on runway 12R and told NCT to put Aircraft Y on an approach to runway 12L.Aircraft X checked on and I cleared him to land on runway 12L. As Aircraft X completed his landing roll; I instructed him to hold short of runway 12L for landing traffic. As Aircraft Y completed his landing roll; Aircraft X said; 'Be advised; we're sticking out a little onto runway 12L'. Aircraft Y heard this and said; 'That's OK; we won't hit you.' I should have advised Aircraft Y to give Aircraft X more space so they could both land on runway 12L. Furthermore; had Aircraft X informed me of his position; I would have had time to instruct Aircraft Y to go around.




Synopsis: SJC Tower Controller reports of a runway incursion with an aircraft landing on the left runway while the aircraft on the right has passed the hold short lines.
Date: 201510
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Diverted; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In cruise I noticed a couple of pin point sized orange glows at the bottom of the Captain's forward windshield. Looked at it with flashlight and we could tell that they were coming from a small area of delamination at the base of the windshield. As the frequency and size grew we agreed they were being caused by the windshield heat. We ran the QRH which directed us to secure the forward windshield heat. We notified maintenance that we were doing so. Within a few minutes of turning off the heat we heard a loud pop and the windshield had shattered. We [advised ATC] and start a descent to 15;000. After reviewing our options we decided to divert to [a nearby suitable airport]. FO did an excellent job getting aircraft down and configured while I did FMS work and notified [operations].Cause [was a] fault in the windshield heat system.I understand from talking to the duty officer and maintenance that we have had a rash of the shattered windows recently.




Synopsis: B757-200 Captain reported his forward windshield shattered in cruise flight. Flight diverted to a suitable alternate.
Date: 201304
Local time of day: 0601-1200
Location: RNO.Airport, NV
Flight conditions: VMC
Weather elements / visibility: 30
Light: Daylight
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C RNO
ATC / advisory: TRACON RNO
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer
Human factors: Situational Awareness
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were cleared for the visual approach to Runway 16L at RNO. We briefed and were using the RNAV (GPS) X Runway 16L approach as a backup since it was my first time ever landing on 16L. Approximately 2 NM north northeast of SEKAW; I inadvertently descended approximately 200 FT below the required crossing restriction of 7;200 FT at SEKAW. [I] disconnected the autopilot and corrected back to 7;200 FT. As we began correcting; Approach Control advised us of a low altitude alert and asked if we had the terrain in sight. We confirmed that we had the terrain in sight and were correcting. We crossed SEKAW at 7;200 FT and completed a normal approach and landing. Preventive: confirm meeting SEKAW crossing restriction prior to arming APPC mode on RNAV approach.




Synopsis: A319 Captain reported descending below charted altitude on visual approach to RNO prompting a low altitude alert call from ATC. Flight returned to charted altitude and continued approach.
Date: 201403
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Aircraft Furnishing
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer
Human factors: Communication Breakdown; Distraction; Confusion
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Company Policy
Primary problem: Aircraft

Narrative: I don't know where else to submit this; nor do I know if the Company is aware of the issues with the WiFi. The WiFi is interfering with communication over the COMM's. It randomly produced constant static (broken squelch). Turning it off instantly solves the problem. The recent Crew Bulletin addresses not resetting the WiFi due to the 'experience for passengers.' How about the pilot's ability to hear ATC? What is being done to address the obvious issue?




Synopsis: A B737 Next Gen COMM system was receiving static from the aircraft's WiFi system but a Company bulletin advised not turning it OFF out of concern for their passenger's experience.
Date: 202009
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Passenger boarded with mask not covering nose. A FA asked her to put it over her nose and she wouldn't comply. I approached her and reminded her that the mask is now required even though she claimed a medical exemption. I also reminded her that she agreed to our mask policy when she checked in. It had been under her chin and she moved it up over her mouth but left nose exposed. She then claimed our policy was over the top and I let her know that all major airlines had the same policy. Operations agent was informed of all of this but the woman was now wearing the mask properly; so she was allowed to stay. During the flight the woman was observed many times with the mask under her nose. The decision was made to have a Supervisor meet the flight in ZZZ. The Captain was notified; but failed to call for a Supervisor. This passenger's behavior was also intimidating towards crew members and refused to adhere to safety requirements.




Synopsis: Flight Attendant reported a passenger was non-compliant with face mask policy.
Date: 201809
Local time of day: 1801-2400
Location: SBGR.Airport, FO
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Hit with green laser during climb out of SBGR.




Synopsis: B777 Captain reported being targeted by a laser departing SBGR.
Date: 201901
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: FMS/FMC
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Dual FMC (Flight Management Computer) failure. We thought the FMC's would come back in a minute or two; but they did not. We called Center and asked for vectors back to [departure airport]; explaining our dual FMC failure. We went through QRH procedures; but were unable to recover the FMC's. CA (Captain) screen was blank. FO (First Officer) could see airport identifiers on his. We had a VTK (Vertical track) and Landing Alt amber lights on the PFD (Primary Flight Display). About 35-40 minutes later; ACARS messages started printing indicating to me; the aircraft thought it was on the ground. I got a close-out deleted and expired messages. I had selected both FMC's to FO side as per QRH with that side giving best information. After the close out deleted message; I was able to reload the Perf Init page and everything came back to normal; except the amber landing alt and no amber hook on CA side. We continued to [departure airport] and landed uneventfully.I suspect the aircraft had a failure which may have been caused by system failure indicating we were on the ground. Or perhaps that was a result of another failure with the FMC's.




Synopsis: B737-800 Captain reported returning to departure airport after experiencing a dual FMC failure.