elihoole/asrs-aviation-reports huggingface dataset:
Date: 201810
Local time of day: 1201-1800
Location: LHW.Airport, GA
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Sport / Recreational
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: Routine Inspection
Result: Flight Crew Became Reoriented
Contributing factors: Airspace Structure
Primary problem: Airspace Structure

Narrative: Flying south of Midcoast Regional airport; [I] saw a drone believed military less than 1 mile from my heading; it then turned north and was gone. On my part better monitoring of MOA space was needed.




Synopsis: Light Sport pilot encountered a UAV near a MOA.
Date: 201412
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Dash 8-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were cleared for takeoff and I advanced levers and commenced takeoff roll. The auto feather armed and the engines continued to increase power. Upon reaching about 70-80% torque; the number one engine low oil PSI master warning light flashed about 3 times. I retarded the power levers; aborted the takeoff and we notified ATC. The low oil pressure light went out and oil PSI remained above 55 PSI. I called for the rejected takeoff checklist. We finished all appropriate checklists; advised passengers; and called maintenance to advise them. We both agreed to taxi back to the gate. We advised ground of our decision and taxied back to gate.




Synopsis: Dash 8-300 Captain reported rejecting the takeoff when he noticed Number 1 engine low oil pressure warning light had flashed several times.
Date: 201809
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
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 D ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Airspace Structure
Primary problem: Airspace Structure

Narrative: [We were] descending for the approach into ZZZ in VMC [when] we got a GPWS (Ground Proximity Warning System) warning to climb for terrain. We got a GPWS warning from the plane. There was a ridge in between us and the airport and we decided to descend to final approach fix altitude slowly so we wouldn't trigger the warning to go off. The Captain disconnected the auto pilot and started a climb; once we were on the other side of the ridge and deemed that a normal approach can be continued; we started a descent and landed as planned. We should have stayed at the MSA (Minimum Safe Altitude) and started the descent on the other side of the ridge since we were coming from that direction.




Synopsis: ERJ First Officer reported receiving a Ground Proximity Warning while conducting a visual approach with the terrain in sight.
Date: 201212
Location: ZZZZ.ARTCC, FO
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Descent
ATC / advisory: Center ZZZZ
Aircraft component: Engine Air Pneumatic Ducting
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Relief Pilot
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; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Descending through FL250; RT BLD DUCT LEAK message was annunciated. Ran QRH procedures - Right bleed- off/Right pack-off/ Right AC - off; declared emergency with ATC and landed uneventfully. I was the Relief Pilot during event.




Synopsis: B767-300 First Officer reports a RT BLD DUCT LEAK msg descending through FL250. QRH procedures are complied with and flight continues to destination for an uneventful landing.
Date: 201909
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: ATR 42
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Cockpit Window
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness; Workload; Distraction
Second reporter function: Pilot Not Flying; Captain
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition; Flight Crew Diverted; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise PF (First Officer) noticed burning mark on left center of windscreen. Crew complied with QRH procedure by shutting off right windshield heater. Crew then noted an increase in size of burn laterally; and a burning smell. Very shortly thereafter; the outer windshield cracked and a loud bang accompanied it. The Captain [notified ATC] and directed the FO [First Officer] to move back to the jumpseat in case the windshield caved in. Captain elected to divert to ZZZ; which was 40 miles to our west and commence the ILS to Runway XX. FO set up the GPS; loaded the approach; briefed the approach; assisted with radio calls; and ran the remaining checklists from the jumpseat. Crew contacted [Dispatch] on the ground after safely parking the aircraft. Identification: visually via scan. Cause: right windshield heater malfunction. Suggestions: possible recommendation from company regarding whether to continue to destination or divert.


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


Synopsis: An ATR-42 flight crew reported the failure of the outer pane of the first officer's cockpit window; resulting in a diversion to the nearest suitable airport.
Date: 201906
Local time of day: 0001-0600
Location: ZDC.ARTCC, VA
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Second aircraft: A319
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness; Communication Breakdown
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure; Company Policy
Primary problem: Company Policy

Narrative: When Aircraft X checked on at 340 he asked for higher. I told him he had traffic overhead but would diverge in about 40-50 miles and I would get him 360 when it was available. Aircraft Y has also had a request for higher and I couldn't give it at the time. Later Aircraft X asked again and said would be willing to turn if necessary. I was looking right at Aircraft Y and remembered he had asked earlier. I had additional crossing traffic for him at 360 and asked if he could accept 380. He said he could and I climbed Aircraft Y to flight level 380 and changed the data block to reflect that. I didn't realize that both Aircraft Y and Aircraft X were on frequency and while I thought the second request came from Aircraft Y it was in fact Aircraft X I was talking to. So when I climbed Aircraft Y; it was Aircraft X who responded to the climb clearance and I didn't catch it. I didn't realize I had the similar call signs until the conflict alert went off. Initially I thought it was a Mode C swap and then I realized what had happened. At that point; I had already lost separation but both aircraft were diverging and Aircraft X was almost above Aircraft Z with his high climb rate. So I turned them both just to provide some extra space.Always make sure to use call signs with every transmission. To the extent possible; do not schedule two flights with nearly identical call signs; to be on the same route at the same time.


Second narrative: While at FL340 the ride was moderate chop and we queried ATC about the rides higher which were better. We requested FL360 and the Controller asked us if we could do FL380 which we could do. He then gave us a climb to 380. We started climbing; and then the Controller asked us what altitude we were cleared to and then gave us a right 20 degree turn and re cleared us to 380. There was an airplane behind and to the left at 360 which also got turned. The Controller then said there was a [Company] flight and that there was some call sign confusion.


Synopsis: ZDC Controller and B777 First Officer reported the wrong aircraft accepted a climb clearance due to similar sounding call signs.
Date: 201808
Local time of day: 1201-1800
Location: ILM.TRACON, NC
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Flight plan: IFR
Flight phase: Cruise
ATC / advisory: TRACON ILM
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: ATC Issue All Types; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: ATC Equipment / Nav Facility / Buildings; Procedure
Primary problem: Procedure

Narrative: Aircraft reported clouds around 020 MSL and needed to get lower to see SUT. Second aircraft was also landing [at] SUT. I got ahead of myself in descending the second [aircraft] too soon. [I should have] referenced the 030 MVA along the route of flight. STARS system will be in place soon and the usage of [land] lines and much clearer maps on the [radar scope] will assist in avoiding MVA situations.




Synopsis: ILM TRACON Controller reported descending an aircraft too early and having it enter a lower Minimum Vectoring Altitude area.
Date: 201306
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: MD-82
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed As Precaution; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [We had a] left engine compressor stall just prior to level off at FL330. Left EPR was 1.97; right EPR was 2.08 left N2 was 87% right N2 was 92% EGTs were equal and stable. Smoke appeared in cockpit and cabin almost immediately. Smoke dissipated after approximately 5 minutes. Consulted and complied with QRH; contacted Dispatch; declared emergency with ATC; and diverted. Engine was operated throughout descent; approach and landing. ARFF met aircraft upon arrival and advised everything looked normal. Center was very helpful and professional. Approach assigned us to fly an ILS which was NOTAMed out of service; when I questioned them about it they assigned us the other ILS approach which we flew and landed on uneventfully.




Synopsis: The crew of an MD-82 experienced a left engine compressor stall just prior to level off and smoke almost immediately appeared in the cockpit and cabin. The QRH was consulted; Dispatch contacted; and an emergency declared with ATC. The aircraft; with both engines continuing to operate; diverted to a suitable airport and landed uneventfully. ATC initially issued a NOTAMED out-of-service runway; but when questioned by the alert flight crew another runway was assigned.
Date: 202108
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 7
Aircraft: Large UAS; Fixed Wing
Operator: Government
Operating under: Part 91
Flight plan: None
Mission: Training
Airspace: Class G ZZZ
Aircraft component: Fuselage Panel
Component problem: Malfunctioning
Reporter organization: Government
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Other / Unknown
Detector: Person Maintenance
When detected: Routine Inspection
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After a recent training flight; maintenance personnel discovered an Avibank (screw) had come off an inspection panel and had hit the propeller. During flight no degradation of flight characteristics were noticed.Damage to prop blade is minimal and can be repaired in accordance with established procedures. No other damage noted.




Synopsis: During a post flight inspection of a UAS; the crew discovered a screw became dislodged and damaged a propeller.
Date: 202108
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 20
Light: Daylight
Aircraft: Extra 200/300 Series
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying; Flight Engineer / Second Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed As Precaution; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Reposition flight for new owner of Extra 300L. In route at 4;500 feet MSL; oil pressure dropped into the yellow. Asked Approach Control for vectors to nearest suitable airfield. Proceeded to gain more altitude in case an engine out approach was needed; it was not. No traffic at uncontrolled airport. Did a descending turn over field and an uneventful landing. Cleared the runway and shut down engine as oil pressure dropped below the yellow arc. Line boy and I pushed aircraft to FBO. Turned over to Maintenance to evaluate.Approach Control was extremely helpful. All the information provided by them allowed me to concentrate on the situation at hand. Asked to contact them after landing to insure I landed safely.




Synopsis: Extra 200/300 pilot reported losing oil pressure inflight and requested vectors to the nearest suitable airfield.
Date: 201906
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Ground Personnel
When detected: Taxi
Result: Flight Crew Returned To Gate; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: After push; the [Load manifest] showed the dangerous goods in pit 2 with only 2 bags. After an unsuccessful attempts by the ramp to final the flight the dangerous goods was moved to pit 1 with only 11 bags. After several more attempts to final; the [load manifest] the bag count in pit 1 was changed to 15 bags and final weights were sent. The flight never came back to the gates to physically move the dangerous goods from pit 2 to pit 1 nor to add bags.




Synopsis: Airline Ramp Personnel reported Hazmat loading configuration error to Dispatch. Aircraft departed without returning to gate to correct Hazmat load.
Date: 201306
Location: IAD.Airport, DC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Pitot-Static System
Reporter organization: Air Carrier
Reporter function: First Officer
Second reporter function: First Officer
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Vehicle
Detector: Person Flight Crew; Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Equipment / Tooling; Human Factors
Primary problem: Equipment / Tooling

Narrative: While performing our preflight checks we heard the aircraft door close then felt the aircraft get bumped; as if by a bag loader or catering truck. We then saw the jetbridge moving in a forward direction past the left cockpit windows. The Captain motioned to the jetbridge driver to stop and not attempt to move the jetbridge. The jetbridge had struck the lower pitot tube on the left side of the nose. A few minutes later when they (gate agent under maintenance supervision) attempted to back the jetbridge away from the aircraft we heard a crunch and ripping of metal as the jetbridge nearly pulled the pitot tube off of the aircraft.


Second narrative: All was normal until just prior to push back. The final checklist was in progress when the Jetway bumped into left side of aircraft prior to push back and bent pitot tubes. The bump was hard enough to feel and I made a comment. The Captain then saw the jetway stopped with the aft edge pad even with the left aft cockpit window. The Jetway driver stopped and called for help. We entered a maintenance code into ACAR's and waited for Maintenance to appear. Jetway was stopped at Captain left window so the Captain opened the window to discuss the situation with mechanics on the jetway. They said the pitot tube was damaged and the aircraft was broken and inoperative. Another CS jetway driver attempted to move the jetway back and it caused further damage to the pitot tubes. It seemed the steering system of the jetway was not working properly. Later a third person was able to get it to move and reposition to the door for deplaning the passengers.


Synopsis: Widebody flight crew and the jetway operator involved describe a jetway contact with the aircraft that causes damage to the pitot tubes.
Date: 201901
Local time of day: 0601-1200
Location: HWD.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Climb
Airspace: Class C OAK
ATC / advisory: Tower HWD
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Less Severe; Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Procedure
Primary problem: Ambiguous

Narrative: When departing HWD heading 010 and approximately 3 nm from the airport; all GPS signal was lost on both Garmin WASS receivers and 1 portable. The signal was restored at about 5nm. The loss of positional awareness may have caused the aircraft to climb above 1500 ft. and into Oakland Class C airspace. This loss of signal also happened on another occasion. During this time period; the RNAV 28L approach was NOTAMed out of service. When I asked the Hayward Tower about the loss of signal - they did not know of the loss of signal. A NOTAM should have been issued that there was GPS signal loss in this area.




Synopsis: C210 pilot reported momentary loss of GPS signal while departing HWD airport.
Date: 202108
Local time of day: 0601-1200
Location: PWM.Tower, ME
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C ZZZ
Second aircraft: UAV: Unpiloted Aerial Vehicle
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: Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Unauthorized Flight Operations (UAS); Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Received report from PWM approach control while on vectors for Runway 11 that aircraft ahead reported a drone 3 miles from end of Runway 11 above their glide path.  We sighted the  drone above our fight path and continued approach.  Drone was hovering around 1;500 feet close to final approach course a 3 miles from touchdown.  Drone was black in color and at least 3 feet in length.  We reported drone sighting to ATC; Dispatch; and Chief Pilot.




Synopsis: Air carrier flight crew was notified by ATC of a UAS near the final approach course. Flight crew saw and avoided the UAS.