elihoole/asrs-aviation-reports huggingface dataset:
Date: 201306
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We encountered a hydraulic leak on our Number 3 System which led to a Number 3 System failure. We ran the appropriate checklists then called [company] on our satcom and agreed that we were safe to continue. The checklist calls for a manual gear extension which we did but the center gear did not extend. We left the pattern; worked the problem. The weather was good. ATC was informed. After exhausting all options we landed. The fire crew inspected our jet after vacating the runway. There was no visible damage.




Synopsis: MD-11 First Officer reported loss of Number 3 Hydraulic System in flight. They ran the procedure; contacted company; and continued to destination where a manual gear extension was performed; followed by a safe landing.
Date: 201211
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Result: Air Traffic Control Provided Assistance; Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Turning to intercept final for the VOR approach; we experienced a right engine failure rolling out of a right turn and leveling off at 3;000 FT when the engines were throttling up from idle. First indication was a pop from the engine followed by a whine down of the engine accompanied by red indications on the EICAS. I then turned off the autopilot and declared an emergency while asking for vectors off the approach to the east. [I] asked my First Officer to run the Engine Failure Checklist to shut it down or look at a restart. While he was rifling through the yellow book; I got on the PA and explained to the passengers what they had heard and that they would get instructions from the flight attendants shortly. I then called the Purser and asked him to do a prep for evacuation with the passengers.When the First Officer was starting the Engine Failure Checklist; the engine restarted on its own and came to idle. We discussed what flap setting would be appropriate and decided on a flaps 20 landing thinking that it may fail again at any time. We requested an ILS to [right runway] knowing it didn't require the 90-degree turn on short final into what might be a failing engine. After landing [the First Officer] gave the 'remain seated' call and we had the fire company determine that there was no further problem before we shut it down and went to the gate.


Second narrative: During the checklist I noticed engine indications were now near normal and the engine had restarted (assumed due to igniters being on). We decided to return to the airport for a visual approach to [the right runway] backed up by the ILS. We configured the aircraft (flaps and speeds) as if on single engine; in case it failed again. The landing was uneventful.


Synopsis: B757 flight crew had an engine failure turning onto final approach. Flight crew requested vectors off the approach and ran the Engine Failure Checklist. Engine restarted on its own and flight crew continued on a visual approach to uneventful landing.
Date: 202103
Local time of day: 0001-0600
Flight conditions: VMC
Light: Night
Aircraft: B737 MAX Series Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Airspace: Class B ZZZ
Aircraft component: Cockpit Window
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician; Inspector
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Training / Qualification; Communication Breakdown; Workload
Second reporter function: Technician; Inspector
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Other Contacted by Supervisor
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Procedure; Human Factors; Chart Or Publication; Aircraft
Primary problem: Procedure

Narrative: I bought off Required Inspection Item (RII) steps on [work card]. Flight deck window EFB mod. The windows were removed from the aircraft and on a table in the hangar where the modification was accomplished. I did not recognize that this work was being accomplished on a [B737] MAX aircraft.


Second narrative: While working overtime in hangar [on] RON [aircraft]; I was assigned to the line and had some time until my first plane was arriving. I offered to help Inspector out on Aircraft X because he had a lot of work for one inspector. I told him I would work with Inspector 3 on the EFB sliding window modification task cards. I have performed this task on many 700/800 series aircraft over the last 2 years. Once the jobs were completed I signed off the 3 task cards and went out to inspect my aircraft on the line. [Later] I was notified by my manager that I was not RII on the [B737] MAX aircraft and was not qualified to sign off those EFB task cards. I have been to the Max difference classes but not the X week Max class. I was unaware I wasn't RII qualified on the Max aircraft.Aircraft X #2 sliding window EFB mods were re-inspected by another ZZZ QC inspector in ZZZ1.


Synopsis: Inspector reported performing RII on cockpit windows and EFB installation on a B737 MAX aircraft without proper authority to perform the inspection.
Date: 201909
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Logbook Entry
Primary problem: Aircraft

Narrative: After exterior pre-flight inspection the First Officer notified me that he discovered the lower aft tip of the left wing split scimitar was missing. I went out and confirmed what he saw and compared it to the right wing and another 737 sitting at the adjacent gate. We looked in our maintenance history on our iPads for the flight to see if it was documented and could not find it. I expected to find an entry in the Long Term Deferred Items but is was not there. I also did a search for 'Scimitar' and found 3 hits; none of which were related to the missing portion of the wing tip. In the meantime; the FO (First Officer) called Maintenance about it and after about 5 minutes; Maintenance said it was in the history and must have fallen off the Long Term Deferred List with no explanation. Maintenance indicated that it had been written up many times.I decided to write it up for the following reason. I was taking the plane on 3 legs of a charter and we would not be anywhere near a normal gate during that charter operation. If; for some reason; the FAA (Federal Aviation Administration) were to ramp check us and notice the missing wing tip and ask for documentation; I did not have any without a cleared recent write up.Damage was caused by a vendor food truck. The repair was considered an acceptable permanent repair per SRM 57-31-01 Fig 201 RPR 2.The problem is that pilots are not trained to identify or recognize an accepted repair such as this. We are trained to identify and recognize things that are missing or not normal such as this. Hence; this is why it keeps getting pinged and written up causing more individual delays down line of when the repair was made.




Synopsis: B737NG Captain reported a discrepancy with the winglet on walk around.
Date: 202103
Local time of day: 1201-1800
Location: OMN.Airport, FL
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke; 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight phase: Cruise
Airspace: Class E F11
ATC / advisory: TRACON F11
Second aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Conflict NMAC
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While at 3;000 feet about 21 miles southwest of Deland (OMN) (and flying southwest enroute to LAL); I saw on my EFB a possible convergence between myself and two other aircraft. The first aircraft; a twin-engine; was at my five o'clock; slightly higher than me; flying southeast. The second aircraft; a single-engine high wing was at my ten o'clock; slightly below me; and flying southwest. I found myself in the middle of this impending convergence; so I turned right and behind the twin; knowing that the aircraft would safely pass me. In this position; I could observe the other two aircraft quickly converge. I could see they still had vertical separation during the convergence until I saw the high-wing perform a climbing left turn towards the twin's path. There was no collision; but I genuinely think neither aircraft saw each other considering the higher aircraft was a twin-engine low-wing and the lower aircraft was a high-wing. I estimate the aircraft were within 500 feet of each other.




Synopsis: Pilot reports a NMAC in cruise flight.
Date: 201411
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28R Cherokee Arrow All Series
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: TRACON ZZZ; Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were conducting a dual IFR training flight with no IFR flight plan in VMC conditions. We requested with approach control a few practice VFR approaches and [advised] that we had the latest weather. Upon completion of the first ILSXX into ZZZ we proceeded with a low approach. We then informed tower of our missed approach and they instructed us to fly the missed approach as instructed and to contact departure. Upon reaching 500AGL the we encountered a partial power loss. The tachometer indicated between 2700 and 1300RPM during the partial [power] loss. We then proceeded with the aircraft emergency checklist which did not correct the situation. We then [advised ATC] and tower cleared us to land on runway XX. Not able to make runway XX we informed tower we were going to land on runway XY; at which then tower cleared us to land on any runway. We landed with no incident.




Synopsis: The instructor and IFR training pilots aboard a PA28R suffered a partial power loss; advised ATC; and landed at the airport where they had been shooting practice ILS approaches.
Date: 201911
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Light: Dawn
Aircraft: B767-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Became Reoriented; Flight Crew Regained Aircraft Control
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Enroute we were at our assigned altitude of FL270 when the aircraft suddenly pitched up uncommanded and went into a climb. The flying pilot disconnected the autopilot and auto-throttle and manually brought the aircraft to the assigned altitude.




Synopsis: B767-200 Captain reported sudden un-commanded pitch-up during cruise.
Date: 201406
Local time of day: 0601-1200
Location: MYF.Airport, CA
Flight conditions: VMC
Weather elements / visibility: Clear; 10
Light: Daylight
Aircraft: Beechcraft Twin Piston Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Descent
Airspace: Class B SAN; Class D MYF; Class E ZLA
ATC / advisory: Tower MYF
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Procedure; Airspace Structure; Human Factors
Primary problem: Airspace Structure

Narrative: I was giving flight instruction in a light twin. I was approaching Montgomery Field in San Diego to give my student a single engine approach using Montgomery Field's ILS in VFR conditions. I was outside their Class D airspace and above Gillespie Fields Class D airspace. I was waiting for an opening to communicate with Montgomery's Tower when I head a person saying that he almost had a mid-air collision with a twin engine aircraft. At that moment I was able to make contact with Montgomery Tower. They asked me if I had just seen an aircraft go by. I told them I had not seen anything. They gave me permission to use the ILS for the approach and then gave me permission to land. The other aircraft was asked if they wanted to report a near mid-air and they said they would when they returned. About 2 hours later I received a call to contact the Tower. I made contact and they asked me questions about this incident. They told me that the reporting aircraft said that he was 50 FT above my aircraft and about 100 yards to the right of my plane. They also said that at the moment of the near mid-air they became very busy and could not give traffic advisories at that time. I gave them all the facts that I didn't see the other aircraft and what my altitude and heading were. I was informed that there was no pilot deviation; but need my information as when a near mid-air is reported they had to file a report. The problem with that airspace around Montgomery Field is San Diego's Class B airspace the Gillespie Field's airspace is that all traffic is funneled into a very small space of sky trying to get to Montgomery Field without talking to anyone.




Synopsis: Twin Beechcraft instructor pilot; above Gillespie Fields class D airspace; is informed by ATC that he may have had a NMAC. The reporter laments the very constricted airspace.
Date: 201910
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Failed; Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Time Pressure; Situational Awareness; Distraction
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Diverted; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; Flight Crew Took Evasive Action; General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were climbing through FL200 when the Left Pack seemed to fail (the right pack was currently deferred and inoperative). There was a depressurization followed by an immediate descent to 10;000 ft. Appropriate checklists were run which entailed the passenger oxygen masks would drop down. The decision to return to ZZZ was made shortly after and then unfortunately; fumes and smoke were detected next and a diversion to ZZZ1 was safely executed. Checklists were done appropriately; a [diversion] brief was made; passengers briefed to the situation; and an aircraft deplaning through the main cabin door in a walking manner was made with everyone. An expedited deplaning checklist was run and the aircraft shut down and secured after everyone had left.The cause was suspected to be a remaining PACK failure.This was unexpected and the only thing that may have prevented this was having a shorter time period for the MEL for the R PACK deferral.


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


Synopsis: CRJ-200 flight crew reported a pack failure that resulted in a cabin decompression and a diversion.
Date: 201908
Local time of day: 1201-1800
Location: OAK.Airport, CA
Weather elements / visibility: Haze / Smoke; 3
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Cruise
Airspace: Class C OAK
ATC / advisory: Tower OAK
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Personal
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Exited Penetrated Airspace; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: Had to deviate from course to the left to avoid what looked like a drone and may have briefly encroached a TFR area (Cal Berkley Football Stadium) to avoid contact with this object.




Synopsis: C172 Instructor reported deviating to miss a possible drone resulting in TFR encroachment.
Date: 201603
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B747 Undifferentiated or Other Model
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: Air Data Computer
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Human factors: Other / Unknown
Second reporter function: Pilot Not Flying; Relief Pilot; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Approximately 1:30 hours into our flight the first officer lost all of his flight instruments. We discovered we lost the right Air Data Computer. The first officer selected left on his Air Data switch located on the instrument source select panel to recover his airspeed; altimeter and VSI to his PFD (Primary Flight Display).We called dispatch to get a 3 way call with maintenance. Maintenance told us it's Captains emergency authority to pull and reset the Air Data circuit breaker. Since there was NO GUIDANCE in the QRH to deal with a lost Air Data Computer I pulled and reset the circuit breaker to no avail.I made the decision to return to ZZZ based on the fact I pulled the Air Data circuit breaker; and did not want fly and additional 12 hours on one Air Data computer.We coordinated our return with dispatch and ATC. We started dumping fuel 80 miles out at 31;000 feet. We then flew a normal arrival and approach.


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


Synopsis: The Right Air Data Computer on a B747 failed and the Crew elected to return to the departure airport.