elihoole/asrs-aviation-reports huggingface dataset:
Date: 201908
Local time of day: 1201-1800
Flight conditions: VMC
Weather elements / visibility: 5000
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Training / Qualification; Situational Awareness
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors; Weather; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: [My] seaplane landed long and touching down past the target beamed point with added forward momentum that extended the stop point. [This] resulted [in] impact with a pontoon boat and damages to floats.  Started a second path over the lake as a downwind path over the far right of the long side of the lake to review boat traffic and evaluate wind and water conditions. After identifying a target landing path of over 2500 ft and touchdown point then started my base to final turn and lined up with high trees to my right and LVR (Landing Visual Reference). As I descended below the tree line with 10-degree flaps and following procedure to evaluate my altitude over water with peripheral vision and manage sink rate at the time of the flare when reaching ground effect. A target of landing within 1000 ft and maintain 300 to 500 added distance to taxi forward to a sandbar where many boats set up. The weather condition; hot; humid; with light variable wind; possible wind changes to a tailwind; alignment to a straight wall of tall trees on the right side where the beamed target point was harder to recognize below the tree line. [The] high [and] somewhat narrow terrain around this lake made spacing left/right during approach important to a straight landing path.




Synopsis: GA pilot reported low speed contact with pontoon boat after a water landing.
Date: 201201
Local time of day: 1801-2400
Location: ZOA.ARTCC, CA
Aircraft: B747-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZOA
ATC / advisory: Center ZOA
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [We got an] EICAS 'trim valve' message. Procedure is to reset once; then; if unsuccessful; turn off 'Trim Air.' The reset was unsuccessful and we turned the trim air off. Cabin temperature was uncontrollable; with Maintenance Control guidance used Captain's Emergency Authority to reset associated circuit breakers but this was unsuccessful. We continued with two pack operation in auto and/or manual as required to warm the cabin. This was acceptable but the cabin remained very cool and the passengers used blankets and coats as a supplemental source of warmth.




Synopsis: When the automatic air conditioning system malfunctioned enroute; the flight crew of a B747-400 utilized alternative methods to mitigate the loss of temperature control.
Date: 201811
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Autoflight System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Commercial
Human factors: Human-Machine Interface; Workload; Communication Breakdown; Distraction
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Flight was descending into ZZZ via the ZZZZZ3 Arrival. Passing 11;000 [feet] on the descent; the Autopilot Mode Control Panel locked up. All Mode Control Panel displays showed 888. All mode control inputs; heading; speed; altitude; became inoperable. Autopilot and auto-throttles failed. The altitude alert sounded continuously. Aircraft was then flown via raw data. Pilot Monitoring informed ATC we lost the Mode Control Panel. ATC directed us to descend and maintain 3;500 [feet]; thus removing all the crossing altitudes associated with the arrival. ATC also started vectoring us.After things settled down; Pilot Monitoring consulted QRH and as we suspected; there was not a NNC (Non normal checklist) that addressed this scenario. During the descent; we became concerned about the reliability of the IAS [Indicated Airspeed]. When trying to slow it; seemed that the IAS was not responding normally. Crossing checking all systems; Captain; First Officer; [and] Standby showed IAS was same. As we finally slowed and started to configure for the approach; the IAS indications started to respond normally. We received vectors for ILS XXR at ZZZ. Approach was flown via raw data and landing was uneventful.  After blocking in; MX Control was informed and Mode Control Panel discrepancy entered in logbook. Local MX performed a hard reboot of aircraft; total power down and power up. This cleared the fault and logbook was cleared. We completed the last leg without further incident.Note: the altitude alert sounded continuously from the time of Mode Control Panel failure to aircraft power down. Reflecting on the incident; I think if it were to happen again I would have declared an emergency so as to give us more time. Also I think it would help ATC understand just how much our workload increased. I don't think we communicated to the controller just how busy we were because of this malfunction.




Synopsis: B737 Captain reported a mode control panel failure led to distraction and high workload.
Date: 201402
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Light: Dusk
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: MD-80 Series (DC-9-80) Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Communication Breakdown
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight; Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: We broke out about 600 AGL and both the First Officer and I noticed an aircraft was in position holding but we had been cleared to land. The First Officer queried Tower if an airplane was holding on the runway. The aircraft on the runway answered in the affirmative and we initiated a go-around from below 500 FT as Tower issued us go-around instructions. We executed the go-around and came back around the pattern and landed safely. Had visibility been more restricted; this could have been disastrous.


Second narrative: Told by Tower to line up and wait on [Runway] 36C. While waiting on the runway we heard another aircraft warning that there was an aircraft on the runway (us) and then Tower ordered a go-around of a heavy aircraft which we heard fly right over us. Then Tower cancelled our takeoff clearance [although] we had only received a clearance to line up and wait. After wake turbulence separation we were then cleared for takeoff.Tower must slow down when the weather moves in and check the separation between landings and takeoffs.


Synopsis: A serious ground conflict occurred when an MD80 flight crew understanding they were cleared only to LUAW on the active runway; remained on the runway when an A330 broke out of the overcast on final about 500 AGL. An aircraft holding short noted the conflict and alerted the conflicted aircraft and ATC. The landing aircraft executed a go-around. ATC believed the LUAW aircraft had been cleared for takeoff.
Date: 201904
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: Turbulence; 10
Light: Daylight
Aircraft: J3 Cub
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Climb
Airspace: Class G ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Sea; Flight Crew Private; Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Diverted; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Piper J-3 Cub on EDO floats departed water and suffered power loss at a low altitude and returned to land at departure point. Pilot had departed [state] previous day and was flying the plane to [another state]. Aircraft landed for a planned fuel stop prior to departure.Pilot completed a run-up and checklist items and had conducted step taxi to departure position at takeoff power settings prior to departure. Plane climbed to an altitude of approximately 500 feet AGL and 300 feet above a tree ridge at end of climbout before turning toward on course heading. Upon turning; the engine ceased producing power. Pilot employed carburetor heat; switched fuel tanks; and cycled magnetos with no resulting change in engine power production.Aircraft returned to area of departure and made initial contact with surface on the mudflats near the edge of the water body from which it departed. Aircraft continued across mudflats to the water; remaining upright on floats at all times. In the course of landing the left wing collided with an upright of an unoccupied boat slip. No damage was caused to boat slip. Observable damage was caused to outer left wing leading edge of the aircraft. Damage did not appear to be of a level to require major repair.Post flight sumping of right tank indicated some contaminants; however; no contamination was noted in post flight sumping of the plane's gascolator or left tank. Plane was able to be restarted after landing at idle and aircraft was moved from landing area to tie down area under its own power and control after landing.




Synopsis: Piper J-3 Cub pilot reported engine failure shortly after takeoff.
Date: 201811
Local time of day: 0601-1200
Location: DEN.Airport, CO
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B DEN
ATC / advisory: TRACON D01
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Second reporter function: Captain; Pilot Flying
Anomaly: Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Ambiguous

Narrative: A drone passed us about 500-700 feet below us and about 1000 feet to the aircraft's right as we were doing a visual approach.


Second narrative: While approaching DEN from the SE; on a right base for Runway 35L; we saw what appeared to be a drone approximately 500 feet below and to our right. We were level at 11;000 feet. The drone appeared to be in the shape of an octahedron; approximately two feet by two feet in size; and was heading east. We reported it to ATC.


Synopsis: Air carrier flight crew reported a conflict with a Drone on approach to DEN.
Date: 201905
Local time of day: 1801-2400
Location: DTW.Airport, MI
Aircraft: Embraer Jet Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: Center ZOB
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness; Confusion
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure; Chart Or Publication; Aircraft
Primary problem: Aircraft

Narrative: After getting cleared direct to KZLOV on the LIDDS1 departure the next 2 fixes apparently somehow dropped out of the flight plan unknown to us. The full departure was loaded in the FMS and checked.  We were told we did not have to follow the altitude restriction and to resume normal speed.  We were on course to LIDDS and then apparently NOONR and ZEYOU were missing; as Pilot Monitoring I did not notice that and we were on course for GRIVY when ATC asked.  After speaking with the Center Duty Manager he indicated to me that this has been occurring and they are trying to figure out why.  It appears that the database dropped those fixes which is what he indicated other crews have told him.  We departed Runway 22L and again we had checked the fixes. This should be added to 10-7 company pages to watch out for.


Second narrative: Second narrative contains no additional information.


Synopsis: A Flight Crew reported two fixes in their flight plan dropped out of their FMC causing them to fly off course.
Date: 201601
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Brake System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Rejected Takeoff; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon initial takeoff roll; FO (First Officer) as PM (Pilot Monitoring) noted Brake Sys Fault 1 ECAM; low speed rejected takeoff performed. Taxied clear of runway to holding area and contacted Maintenance for action. Performed actions per Maintenance. Normal operation restored. Obtained new Maintenance release. Completed checklists and flight was resumed.




Synopsis: Brake system fault light illuminated at initial take-off roll. Aircrew rejected the take-off at low speed.
Date: 201510
Local time of day: 1201-1800
Location: DAB.TRACON, FL
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class C DAB
ATC / advisory: TRACON DAB
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Developmental
Human factors: Situational Awareness; Confusion; Distraction; Human-Machine Interface; Workload
Anomaly: ATC Issue All Types; Deviation - Speed All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; General Maintenance Action
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: A Mooney was inbound to a satellite airport from the South; handed off from F11 [Orlando TRACON]; at 5;000 feet. Once the aircraft was in the vicinity of SMYRA; abeam EVB and X50 airport; the tag began to jump consistently. I observed the tag move in all different directions at varying speeds up to 300 knots or so. I attempted to change the radar mode from fusion to DAB site and the issue persisted. I had the aircraft ident and confirm altitude to ensure his identification. The anomaly eventually resolved itself; but the situation could potentially be dangerous and highly distracting during periods of heavy traffic. This is one of several instances occurring recently and appears to be happening in the same area.I recommend these instances be logged and reported to the radar technicians until the radar anomaly can be identified and resolved.




Synopsis: Controller observed aircraft radar data tag jumping off the aircraft target in different directions and indicating false airspeeds. Reporter states this has occurred other times in the same area.
Date: 201501
Local time of day: 0001-0600
Location: SCT.TRACON, CA
Light: Night
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class E SCT
ATC / advisory: TRACON SCT
Second aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction; Confusion; Time Pressure
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Air Traffic Control Provided Assistance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X released from VNY airport.  Aircraft X airborne reported out of 1;700 for 4;000 per SID; radar ID'd and told to climb and maintain 14;000 feet.  Released Aircraft Y from BUR airport.  Aircraft X doesn't follow SID; flies runway heading level at 1;700.  Issued follow up instructions to climb and maintain 14;000 with an expedite thru 5;000 for terrain and turn left to 320.  Aircraft X slowly starts his turn but stays level causing a Low Altitude alert to happen.  Issue a low altitude alert to Aircraft X and told to climb and turn immediately.  Aircraft Y departs BUR leaving 1;700 for 4;000 as well.  Turn Aircraft X southbound to avoid Aircraft X.  Called traffic to Aircraft X and Aircraft Y to each other and got visual separation from both but unsure if I had standard separation before getting visual separation.  Aircraft X turned and slowly climbed and both aircraft proceeded without further incident.Have Aircraft X follow the SID reference headings; altitudes; and takeoff minimums for climb out.




Synopsis: SCT Controller reports of an aircraft that departs but doesn't follow the SID on climbout. Aircraft turns slowly causing a loss of separation with another aircraft departing a close proximity airport.
Date: 202102
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 150
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Aircraft component: Brake System
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were practicing touch and go's and at the last landing we tried to brake the aircraft and I felt that the left brake was not working.  I communicated to the Tower that I could not turn to the left so they cleared me to turn to the right.  I cleared the runway on taxiway Alpha and I tried to stop the aircraft but we couldn't and we did the full stop at the grass. We didn't hit any light or nothing to be considered damaged. Airport operations went to the place and they saw that everything was good.




Synopsis: C150 flight instructor reported during touch and go training with student; there was brake failure after landing.