Peacocks are overwhelming an Orlando neighborhood: ‘There's feces everywhere'
Residents at the Villas at Costa del Sol are angry about a bunch of peacocks who they say are damaging property and creating safety concerns by defecating all over the neighborhood and chasing local children.
The frustrated Floridians said the problem began years ago when a resident introduced a pair of peacocks into the community. The birds reproduced, adding more and more peacocks to the area over the years.
Now the birds are numerous, and are reportedly causing issues.
'There's feces everywhere and the kids play in the ground, you know that has so much bacteria, so that's one of the things we're worried about. They go after the kids, like if the kids were with their family and they're playing, they just run after them,' Maria Calderon, the volunteer HOA president at the Villas, told News 6 Orlando.
The birds aren't just scaring children and leaving droppings; they're also reportedly scratching up residents' vehicles and damaging their homes.
According to Calderon, the birds see their reflections in the car panels and try to fight their reflections, leaving scratches and beak marks. One resident reportedly had to spend thousands to repair their car, and later switched to a lighter-colored vehicle that was less reflective to avoid bird attacks.
'They scratch your car because they think they're fighting,' the resident, who chose not to provide their name, told the broadcaster. 'All I hear is THUD THUD THUD cause they're pecking it with their beak, and they go to the other side of the car cause they think they'll get to that other bird. And then they're not just pecking at it, they're jumping up and they're scratching it.'
Another resident, named Victor, told the outlet that birds have torn at his screen door and have flown onto his roof, forcing him to replace two tiles already.
Unfortunately for the residents, if they want the birds gone, they'll have to foot the bill. The city of Orlando, Orange County, and the Florida Fish and Wildlife Conservation Commission have all said that removing the birds is the responsibility of the residents.
That's easier said than done; Calderon said she's tried numerous public and private groups asking for help, but hasn't found anyone willing to take on the task. She said few organizations she's spoken with have the capacity to house the large number of peacocks loose in the area.
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
The Guardian
3 hours ago
- The Guardian
Worried about your child's screentime? Get a landline
Among the many useless but consoling facts I've hung on to at the expense of real knowledge is the telephone number of my best friend from high school. I can say it in my head – 612505 – and, like a combination lock, it throws open the door to a memory of me sitting on the stairs after school, yakking to the person I'd just said goodbye to on the bus. Given it's more than 30 years since I used that number, I have to assume it will stay with me – along with the lyrics to the Cadbury's Roses ad from 1983, the name of the fictional head teacher of Summer Bay High (Mr Fisher) and my own telephone number from that era (623492) – until the day I die. I hadn't given much thought to landlines or the teenage experience of sitting on them after school every day, until a recent piece in the Atlantic shared the results of a small, highly localised experiment: in Portland, Maine, a parent nervous of giving her 10-year-old child a smartphone took the eccentric step of reintroducing a landline, and then persuaded the parents of her child's friends to do the same. Before she knew it, between 15 and 20 families in the area had reinstalled landlines for their preteens in what the Atlantic called a 'retro bubble'. Charming scenes ensued, communications habits changed, and everyone learned a valuable lesson about the advantages of ancient technology. The funny thing about this is that unlike the brick phone, another answer to the puzzle of how to keep children off social media, the families of Portland discovered that the very thing that limits the landline – the fact it's attached to the wall – turned out to be one of its big attractions. Most families put the phone in a high-traffic area of the house, keeping their kid at least notionally in the mix rather than shut away in their room. This was a tactic popular in the early days of home computers, when parents would put the family's single, giant desktop on a table in the kitchen so the kid wasn't isolated or left alone with 'the internet', a healthy instinct that smartphones effectively killed. For the kids involved, pivoting to landlines entailed a conceptual leap as big as any they'd encountered: the amazing Russian roulette of having to pick up a ringing phone to discover who was on the other end; the mediation experience of having to say hello to a parent and ask politely to be put through to their child; the need to memorise a number; and the wildest thing of all, trying to remember that phoning a friend on a landline meant that, if they picked up, they could only possibly be in one place, so that shouting 'ARE YOU HOME?!' down the phone, as one young case study did, made no sense whatsoever (but was very funny). None of the families involved had an interest in reducing the contact their children had with their friends. But they were concerned with the issue of distraction – that kids speaking to each other on smartphones are often scrolling at the same time – and one of the reported findings was that the old-fashioned phones encouraged them to become 'better listeners'. For anyone who grew up getting home from school, changing out of their uniform and getting straight on the phone to carry on the conversation they'd broken off an hour earlier, this idea of extracting formal skills and takeaways from basic behaviours seems part of the broader parenting shift towards turning every last thing into an effing learning experience. On the other hand, I get it; the appeal of old phones is rooted in nostalgia but also in the idea that there is something wholesome about the relative transparency of landlines and returning to a way of doing things that, while it annoyed parents back in the day, didn't strike the fear of God into them. Pre-mobile phones, the main anxiety suffered by parents with kids who were forever on the phone was that they were going to 'run up the bill', 'tie up the line', or fritter their life away gossiping, all adorably quaint concerns. No one can groom or catfish a child via a hunk of plastic attached to the wall. What was the takeaway for us, who grew up on landlines? I guess if mobiles these days exert an enormous gravitational pull in our pockets, still some other order of magic existed around the old landlines. 'I'll get it!'; 'it's for me!'; redundant phrases now that, back then, spoke to the tiny thrill of election that came from receiving a call via the family phone – and like ghosts from the deep past, the lifelong dedication to memory of the numbers. Emma Brockes is a Guardian columnist
Daily Mail
4 hours ago
- Daily Mail
Horrifying new video showing Black Hawk's deadly mid-air crash with American Airlines jet is played at hearing as final words of chopper pilot are revealed
A horrifying video showing the moment a US Army Black Hawk helicopter smashed into a passenger jet over Washington, DC, has been released, as investigators reveal the final words of the doomed crew. The footage, captured by CCTV and played at the start of a three-day National Transportation Safety Board (NTSB) hearing, shows a bright flash lighting up the night sky above the Potomac River. Seconds earlier, the military chopper had collided with American Airlines Flight 5342 as it descended into Reagan National Airport. The Bombardier CRJ700 had been flying from Wichita, Kansas, on January 29 and was just minutes from landing when it was hit. All 67 people on board the two aircraft were killed, including 63 passengers and crew on the jet and four helicopter crew members, marking the deadliest US airline crash in more than two decades. The Black Hawk, operating as Priority Air Transport 25, had been on a low-level training mission and was flying back to Fort Belvoir in Virginia. Investigators now believe the crew thought they were flying 100 feet higher than they actually were due to faulty altimeter readings. The NTSB revealed that about three minutes before the crash, Chief Warrant Officer Andrew Eaves told co-pilot Capt. Rebecca Lobach to 'come down for me' and fly at 200 feet because they were currently at 300 feet. The footage was captured by CCTV and played at the start of a three-day National Transportation Safety Board (NTSB) hearing All 67 people on board the two aircraft were killed, including 63 passengers and crew on the jet and four helicopter crew members The route down the river on which the chopper was on has a maximum altitude of 200 feet near the airport, according to the NTSB's presentation. Two minutes before impact, air traffic control warned them about the approaching passenger plane. A second warning followed 90 seconds later. In both times, the helicopter crew told controllers they could see the jet and asked for 'visual separation' to allow them to navigate around the flight. The controller also told the helicopter to pass behind the passenger plane, but that instruction was not heard by the crew. Twenty seconds before the crash, Eaves said: 'Alright, kinda come left for me ma'am, I think that's why he's asking.' Lobach replied: 'Sure.' Eaves added: 'We're kinda out towards the middle.' Lobach responded: 'Okay fine.' The helicopter and the jet collided at 8:48pm, causing a bright fiery flash in the night sky. Meanwhile, in the American Airlines cockpit, the pilots used expletives when they saw the impending crash and attempted to pull the plane up just seconds before. NTSB investigators later carried out test flights using three similar helicopters over the Potomac. They found that downwash from the rotor blades consistently interfered with barometric altimeter readings, making it appear they were higher than they really were. The board also heard the Black Hawk crew had been suffering from burnout, raising fresh concerns about their decision-making on the night of the crash. Air traffic controllers have also come under scrutiny following reports that there were staffing problems at the airport on the day of the crash. Thousands of pages of records have now been made publicly available as part of the investigations.
The Independent
9 hours ago
- The Independent
Day 2 of federal investigation into fatal midair crash of Army chopper, commercial plane opens
The National Transportation Safety Board enters a second day of public hearings Thursday on the January midair collision between an Army Black Hawk helicopter and a passenger plane that killed all 67 people aboard the aircrafts. On the first day, investigators highlighted a number of factors that may have contributed to the crash and the warnings about helicopter traffic that FAA received years before the tragedy over the Potomac River. It's too early for the board to identify what exactly caused the crash. The board's final report won't be released until sometime next year. But it became clear Wednesday how small a margin of error there was for helicopters flying the route the Black Hawk took the night of the nation's deadliest plane crash since November 2001. The January incident was the first in a string of crashes and near misses this year that have alarmed officials and the traveling public, despite statistics that still show flying remains the safest form of transportation. FAA didn't add warning to helicopter charts, official says NTSB Chairwoman Jennifer Homendy said an FAA working group raised concerns about all the helicopter traffic around Reagan airport and the risk of a collision in 2022, but the FAA refused to add a warning to helicopter charts urging pilots to use caution when this runway was in use. 'This is the very event that this would have been the cautionary note for,' she said. Video and animation presented during the proceeding's first day showed the helicopter flying above the 200 feet (61 meters) altitude limit before colliding with the plane. Investigators said Wednesday the flight data recorder showed the helicopter was actually 80 feet to 100 feet (24 to 30 meters) higher than the barometric altimeter the pilots relied upon showed they were flying. So the NTSB conducted tests on three other helicopters from the same unit in a flight over the same area and found similar discrepancies in their altimeters. Dan Cooper with Sikorsky helicopters said that when the Black Hawk helicopter involved in the crash was designed in the 1970s, it used a style of altimeter that was common at the time. Newer helicopters have air data computers that didn't exist back then that help provide more accurate altitude readings. Chief Warrant Officer Kylene Lewis told the board that she wouldn't find an 80 to 100 foot discrepancy between the different altimeters on a helicopter alarming because at lower altitudes she would be relying more on the radar altimeter than the barometric altimeter. Below 500 feet (152 meters), Lewis said she would be checking both instruments and cross referencing them. Army officials said a discrepancy of 70 to 100 feet (21 to 30 meters) between the Black Hawk's altimeters is within the acceptable range because pilots are expected to maintain their altitude plus or minus 100 feet. Concern about distances between planes and helicopters The greater concern is that the FAA approved routes around Reagan airport that included such small separation distances between helicopters and planes when planes are landing. 'The fact that we have less than 500 foot separation is a concern for me,' said Scott Rosengren, who is chief engineer in the office that manages the Army's utility helicopters. During the two minutes before the crash, one air traffic controller was directing airport traffic and helicopters in the area, a task that involved speaking to or receiving communications from several different aircraft, according to the NTSB's History of Flight Performance Study. The air traffic controller had spoken to or received communications from the Black Hawk helicopter, an airplane that was taking off, an Air Force helicopter, an airplane on the ground, a medical helicopter and an inbound flight that was not the American Airlines plane that would crash. 'All aircraft could hear the controller, but helicopters could only hear other helicopters on their frequency and airplanes only other airplanes,' the report stated. 'This resulted in a number of stepped on transmissions as helicopters and airplanes were not aware when the other was communicating.' Stepped on transmissions are those that are unheard or blocked because of other transmissions. The NTSB report provides a list of 29 separate communications between the airport tower and other aircraft during approximately the 1 minute and 57 seconds before the collision. Previously disclosed air traffic control audio had the helicopter pilot telling the controller twice that they saw the airplane and would avoid it. The animation ended with surveillance video showing the helicopter colliding with the plane in a fiery crash. Investigations have already shown the FAA failed to recognize a troubling history of 85 near misses around Ronald Reagan National Airport in the years before the collision, and that the Army's helicopters routinely flew around the nation's capital with a key piece of locating equipment, known as ADS-B Out, turned off. ___ Associated Press writers Leah Askarinam, Ben Finley and Rio Yamat contributed to this story.
