elihoole/asrs-aviation-reports huggingface dataset:
Date: 202010
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Airspace Structure; Company Policy; Human Factors
Primary problem: Company Policy

Narrative: Aircraft X advised me that he would be flying VFR at a low altitude. He appeared to be following a typical flight path used by VFR aircraft in the area. The aircraft cut through the northern tip of [two airport's] airspace; which too is a common flight path and a common practice. As the aircraft neared [a visual waypoint]; one of the airport's tower controllers called my line to advise that one of their aircraft who was primary only had Aircraft X in sight. Controllers typically observe VFR fly through this northern tip of [their] airspace at low altitude many times a day; every day; without point outs. As this was no different than typical operations in the facility; I did not perceive that there was a problem; until the CIC notified me that Tower had called to report an airspace violation. In the future I will either instruct VFR aircraft to avoid this small section of airspace; or I will point out the aircraft to the appropriate tower before the aircraft enters the airspace.




Synopsis: TRACON controller reported aircraft conflicted with a towered airport's airspace.
Date: 202008
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Flight Crew
When detected: Pre-flight
Result: Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Very near to scheduled departure time; the Flight Crew was verbally informed that there was an aircraft battery onboard and the Operations Agent was in process of completing the NOTAC. The Agent was waiting on Tech Ops for necessary information.Approximately 20 minutes later; the Agent returned and explained there was confusion due to the fact that the battery originated on the same aircraft in ZZZ and was scheduled to continue on another aircraft. A short while later I was provided a document that resembled a NOTAC; however; was a single copy and had no place for me to sign; thereby acknowledging the presence of HAZMAT. I requested the proper form; in duplicate; and the Agent graciously agreed leaving once again to gather the proper form.I attempted to find the reference to required notices (NOTAC) in the X manual while the First Officer searched for the recent bulletin that we both recalled being issued referencing the subject. Dispatch was contacted and I agreed to a pen and ink revision to the Release in order to add the note 'HAZMAT on flight - refer to NOTAC'. The Operations Agent returned with the original NOTAC; issued in ZZZ; signed by the original flight's Captain. The Agent had a duplicate copy. I accepted that document; placed it in the aircraft log and proceeded with the flight.Airborne; we continued to research the event and found bulletin XX-YY issued (date). This revised Company procedures to provide a NOTAC for each individual flight.Do not succumb to perceived time pressures until a valid reference can be located. There were many resources called upon in this event including the Flight Crew; Operations Supervisors; Tech Ops; Dispatch; and an additional Operations Supervisor in the Operations Center. Everyone seemed to be in agreement that we were legal to depart once the original NOTAC was obtained. Had we been able to readily locate and reference the policy/bulletin; we would have been able to verify the revised procedure. It was evident we were not the only aspect of this event that was unfamiliar with the revised procedure.




Synopsis: B737-800 Captain reported receiving incorrect Hazmat document (NOTAC) during preflight for onboard cargo. Flight crew persisted until correct revised procedure and correct Hazmat form provided to flight crew.
Date: 201205
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 25
Light: Daylight
Aircraft: J3 Cub
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Approach
Airspace: Class E ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Traffic ahead of us was a Cessna 150 conducting primary training. The 150 was flying a long wide down wind leg; airline style. Keeping close to the airport I flew the down wind leg behind the 150 but half the distance inside the 150. Abeam the numbers of Runway 22 a landing checklist was completed. Carb heat was not selected due to the fact we needed to extend with power to follow the 150. After the Cessna landed and was not a factor; we made our base turn at about 2 miles. Continuing inbound power was reduced to idle. On about a mile final I attempted to add power to continue the approach but none was available. At about 250 AGL; after attempts to obtain power; I decided to land in a large gravel parking lot prior to the runway; thus avoiding property and buildings. The landing was only 100 FT short of the runway; but the airport security fence prevented me from selecting the runway as an option. The aircraft received only minor damage to the propeller and right wing tip due to lightly clipping power lines during the approach. No injuries occurred. Possible cause was carb ice due to the power being at idle on final and the temp due point spread being close together. Corrective action could be to implement a landing checklist at each segment of the pattern instead of just my downwind landing check. Contributing factor may have been the distraction of the other aircraft in the pattern; however this is not an excuse.




Synopsis: Required to extend his downwind pattern leg due to preceding traffic; the pilot of a J3 Cub failed to employ carburetor heat at his usual point abeam the numbers. The engine subsequently failed to respond to the throttle on short final and the pilot diverted to a gravel area short of the runway. Some damage was incurred due to contact with power lines.
Date: 201901
Local time of day: 0001-0600
Location: ZLA.ARTCC, CA
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Military
Operating under: Part 91
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZLA
ATC / advisory: Center ZLA
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X was a scheduled ALTRV [Altitude Reservation] scheduled with the MOS [Military Operations Specialist]. Airspace was not scheduled in the EDST [En-route Decision Support Tool] and the controller missed the ALTRV. The aircraft was a drone with his transponder off. This was coordinated with the MOS and paperwork was distributed to the areas. Airspace should have been scheduled in the EDST and controllers and the FLM [Front Line Manager] should be verbally briefed.




Synopsis: ZLA Front Line Manager reported a UAV was scheduled into an Altitude Reservation but knowledge of it was not posted nor were the Controllers informed.
Date: 201505
Local time of day: 0601-1200
Location: P50.TRACON, AZ
Flight conditions: VMC
Weather elements / visibility: 40
Light: Daylight
Aircraft: DA40 Diamond Star
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class E P50
ATC / advisory: TRACON P50
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Other / Unknown
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Was in cruise on a training flight; just west of Rio Verde community (VPRVC) when I saw a personal drone or UAV of a quad-copter style pass 50 feet away on the left side of my aircraft.  I reported the occurrence to PHX approach.  I was at 6500 feet when I saw the drone.




Synopsis: DA40 Instructor pilot reports a NMAC with a drone at 6;500 feet beneath PHX Class B airspace.
Date: 201707
Local time of day: 1201-1800
Location: EWR.Airport, NJ
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp EWR
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: EWR ramp cleared us in to gate. As we approached the gate; we had two wing walkers and a Marshaller guiding us in. We could see there was a bag cart well inside the Operational Safety Zone (OSZ) on to the left of the aircraft; so we stopped. We signaled to the ramp crew that we needed the cart moved; but they kept trying to marshal us in. I called ops and informed them that we would not be moving until the cart was out of the OSZ. The left wing Marshaller stood next to the cart and gave the all clear signal while the Marshaller signaled us to taxi in; but the cart was too close to the wingtip for our comfort and it was well within the OSZ; although; was a wide body gate. Eventually they moved the cart and we taxied to the gate.




Synopsis: B737 Captain reported holding short of the gate at EWR due to a bag cart in the safety zone and had difficulty having the cart moved.
Date: 201511
Local time of day: 1801-2400
Location: N90.TRACON, NY
Light: Night
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B EWR
ATC / advisory: TRACON N90
Second aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure; Airspace Structure
Primary problem: Procedure

Narrative: Aircraft X was on Final into RWY 22 at EWR. Aircraft Y was on Final into RWY 13 at LGA. On this runway set up LGA arrivals fly at 2;000 ft underneath EWR arrivals at 3;000 ft. Unfortunately this airspace delegation does not take into consideration wake turbulence; and Aircraft X started his descent on his approach before he was 5 miles ahead of Aircraft Y. I recommend EWR can no longer land RWY 22 while LGA is landing RWY 13.




Synopsis: N90 TRACON Controller reported of a loss of separation that he attributed to an airspace delegation that does not take into consideration wake turbulence. Aircraft departed 1000 ft above another aircraft before there was 5 miles of separation.
Date: 202104
Local time of day: 0601-1200
Location: DFW.Airport, TX
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Initial Climb
Airspace: Class B DFW
ATC / advisory: TRACON D10
Aircraft component: Weather Radar
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
Human factors: Situational Awareness
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: Weather event departing from DFW on climb out on vectors out of around 12;000 AC (Aircraft) was hit by lightning on left side; left engine shut down; but spooled back up; then within seconds RT engine was struck by lightning AC lost radar. We [advised ATC and] requested vectors back to DFW. Weather was bad on climb out in all quadrants; departures should have not resumed so quickly. Wait until weather had moved further from the area before resuming departures.


Second narrative: Departing DFW climbing through 13;000 [feet] we enountered a suggested lightning strike. I remember seeing Eng N1 drop then another strike happened then I noticed Eng stall on ECAM.  I initiated a level off and the Capt requested a lower altitude and [advised ATC]. We also asked for vectors due to radar no longer working. During level off I noticed Eng relight and both engines stabilized. We leveled at 12;000 [feet]  between a cloud layer to assess situation. I suggested we return or divert. Capt was concerned about going back to DFW due to weather. After further review and weather ahead and no radar;  we received vectors north to return to DFW as per ATC. We returned to DFW with no further incidents. We were on hold for weather and ATC asked if someone wanted to path find a route through weather due to radar depicting lower returns from storm. Aircraft left and reported good ride then ATC starting releasing all aircraft. I didn't believe storm was far enough but with report of ATC and first aircraft reports we left. Storm was reporting green on radar and lightning just caught us.ATC allowing more space of weather from an airport.


Synopsis: Air Carrier Flight Crew reported Lightning strike during climb.
Date: 201308
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: DC-10 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Initial Approach
ATC / advisory: Tower ZZZZ
Aircraft component: Powerplant Lubrication System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; Captain
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Received 'ENG 2 OIL TEMP HI' in descent. Temperature started in the yellow then jumped to the red range. Temperature top [at] 225 degrees. Temperature was erratic going from 125-225 degrees. Operated and shutdown engine per QRH. Maintenance verified a previous OIL TEMP OUT OF RANGE fault and suspect the PROBABLE CAUSE was an ENG 2 OIL TEMP SENSOR.




Synopsis: An MD-10 flight crew shut down the right engine in response to a high oil temperature warning. Maintenance determined a faulty temperature sensor was responsible.
Date: 202012
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dawn
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Drinkable/Waste Water Syst
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Training / Qualification; Communication Breakdown; Workload
Second reporter function: Technician
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter FOD
Detector: Person Maintenance
When detected: Aircraft In Service At Gate; Routine Inspection
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Human Factors; Chart Or Publication; Aircraft; Procedure
Primary problem: Human Factors

Narrative: During accomplishment of portable water system disinfect done by using ozone cart; as instructed by fellow mechanic assigned as support; (name unknown). I might have improperly connected the water supply line. This happened at ZZZ [Gate] around XA:00 [Date]. As soon as I noticed water coming out of the aft fuselage drain holes; I immediately stopped the re circulation process; notified crew chef; dumped over serviced wasted and requested for assistance form tech crew personnel.Lack of work experience with this specific task on my part; lack of assigned training; inability to complete work interdependently due to not having D1 endorsement and being able to drive on airport premises and move around with equipment and tools. Hostile work environment.Assigned training required to completed before being assigned to perform ozone cards; different diameter or tread pattern on water fill line attainment port preventing from improper installation; picture diagrams included in revised work card; hands on ozone unit classroom training; ZZZ ramp driving credentials; hangar access in below freezing conditions; better gate illumination; larger port markings allowing to differentiate between both ports housed only 3 ft. apart.


Second narrative: I was assigned to drive new transfer AMT's around since none of them had their DR1/3. One group required the 'blue cart' for water servicing; and the tech responsible for the job asked me questions about it. I gave him a basic description of the job; helped hooked the FILL line to the FILL nipple; and showed him the correct adapter for the job and threaded it in to show it was the right fit. After which I left to move other techs around. When I came back to the gate; that's when the results of the improper servicing occurred. The event occurred at [Gate] at roughly XA:00 on [Date] during the cycling phase of the disinfect.


Synopsis: Technicians reported not connecting potable water disinfection equipment to aircraft correctly; causing the aircraft to flood the lower areas.
Date: 201506
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 180 Skywagon
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Training / Qualification
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: My student and I were conducting flight training in a tailwheel aircraft towards his Private Pilot Certificate. He has 60 hours of dual; including a solo flight; in the same aircraft. The winds at ZZZ were 130 degrees at 6 knots at the time and the runway in use was 18. My student landed and we performed a touch and go. We went around the pattern for our second approach and were cleared to land. After a short landing rollout; the airplane started to weather vane to the left towards the crosswind and he applied the right brake to stop the longitudinal rotation towards the side of the runway. The airplane continued to turn and more brakes were applied; causing it to nose over on the runway. The airplane came to a stop with a bent prop and cowling. We climbed out uninjured and waited for the emergency services to arrive. The airplane was recovered a short time later with no airframe damage.




Synopsis: Cessna 180 instructor pilot reported his student lost directional control after landing and the aircraft nosed over; causing damage to the prop and cowling.
Date: 201204
Local time of day: 0001-0600
Location: IND.Airport, IN
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; 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: Entering the ramp at IND a tug with four dollies attached; driving north on the taxiway side of the ramp; almost hit the aircraft as we were preparing to turn from the throat into the ramp taxiway en route to the gate. The tug then turned right and drove across the ramp and went up the other side of the ramp. I believe the tug was inside of our wing tip. I was concerned he was going to be sucked into the number two engine. A van driving down the center of the ramp taxi lane cut in front of the aircraft while the aircraft was in the throat. Aircraft had its taxi lights illuminated. Better education of the ramp personnel as to who has the right of way on the ramp.




Synopsis: An A300 Captain had conflicts with ground vehicles entering the ramp at IND.