top of page

By:

Quaid Najmi

4 January 2025 at 3:26:24 pm

Bhujbal’s chopper lands in Pune parking lot

Mumbai : In what is suspected to be a breach of aviation protocols, a chartered helicopter ferrying Food & Civil Supplies Minister Chhagan Bhujbal from Mumbai to Pune skipped a designated helipad and landed in a vehicle parking lot almost a km away.   The shocker happened in Purandar taluka, where Bhujbal was slated to attend a function marking the 200 th  birth anniversary of the social reformer Mahatma Jyotirao Phule in his home village Khanwadi.   As crowds of bewildered people watched...

Bhujbal’s chopper lands in Pune parking lot

Mumbai : In what is suspected to be a breach of aviation protocols, a chartered helicopter ferrying Food & Civil Supplies Minister Chhagan Bhujbal from Mumbai to Pune skipped a designated helipad and landed in a vehicle parking lot almost a km away.   The shocker happened in Purandar taluka, where Bhujbal was slated to attend a function marking the 200 th  birth anniversary of the social reformer Mahatma Jyotirao Phule in his home village Khanwadi.   As crowds of bewildered people watched from around the sprawling parking lot, the helicopter appeared to drop speed in its flight, flew over some overhead high-tension electric cables, and descended gingerly into the parking lot - raising a thick dust-storm in which it disappeared for seconds - before touching the ground.   Moments later, the Nationalist Congress Party (NCP) senior leader Bhujbal and others stepped out of the chopper, looked around in the unfamiliar territory before several vehicles and police teams rushed there. Minutes before there was chaos and confusion with some locals shouting warnings at the ‘wrong landing’.   Eyewitnesses said that the chopper’s powerful rotors created a thick dust storm and sparked alarm among the people in the vicinity, and many scrambled to the spot to check what exactly was going on in the parking lot.   Later, the Pune Police said that a designated helipad was available for the chopper landing but were at a loss to explain how the pilot missed it and veered off quite a distance away in the vehicle parking space. Subsequently, they asked the pilot to fly it to the correct landing spot.   Shaken and angry local NCP leaders questioned how a pilot flying a VIP on an official trip could mistake a parking lot for a helipad when the weather and visibility was clear. They demanded to know whether the helipad was improperly marked or it was a question of communication or sheer negligence.   The Pune Police indicated that they would report the matter to the Directorate General of Civil Aviation (DGCA) which may take action against the errant pilot and the helicopter company.   “There was no accident. We all emerged safely. The helicopter pilot landed wrongly in a parking lot because the helipad was not visible. All of us are fine and there is nothing to worry,” said Bhujbal, before he was whisked off by his security team.   “There are many faults in numerous airplanes and helicopters, including maintenance issues and other problems. That's why I keep saying consistently that VIPs must exercise caution while flying. Fortunately, an accident was averted today, but that doesn't mean the authorities should be negligent. We expect the government to take urgent precautions.” Rohit R. Pawar, MLA, NCP (SP)

The Missing Middle: The 15 to 50 Problem

Headcount isn’t a leadership system. If decisions still orbit you, growth will lurch … no matter how many people you add.

A founder told me last week, “We’ve doubled headcount and revenue this year. Why does everything feel heavier?”


Because the business outgrew a small-team way of working … but the leadership system didn’t.


What changes with 20, 35, 50 people isn’t just the number of seats. It’s the number of decisions moving at once. If every decision still routes to one or two leaders, growth stops compounding. It starts lurching.


What breaks first (and why)

When a company jumps from “tight crew” to “real team,” three quiet failures show up:

1. Role fog

Everyone is helpful, nobody is accountable. Work moves, outcomes wobble. People ask for “eyes” instead of taking decisions.


2. Decision vacuum

Escalations are informal (“just ping me”). Approvals depend on presence, not rules. Leaders become the emotional backstop: trusted, but never free.


3. Rhythm drift

Reviews happen when someone remembers. Handoffs depend on who’s online. Dashboards show activity, not ownership. Teams look busy; nothing lands cleanly.


None of this is incompetence. It’s design debt.


The leadership system you actually need

Scale doesn’t come from more people. It comes from installing the middle … not as titles, but as a system. Four pieces matter:


1) Role Charters (not job descriptions)

Write one page per manager-level role: scope, decisions they own, what “good” looks like, and where they escalate. If the team can’t point to this without asking Slack, you don’t have it.


2) Decision Ladders

Define what gets decided where. Green = decide and inform. Amber = decide with consult. Red = escalate with context. When this lives in heads, leaders get dragged into amber decisions all week.


3) Escalation Windows

Fixed slots where stuck work is surfaced and resolved … inside the system, not around it. No more 11:17 PM pings. Predictability is what converts “I’ll just check” into “the process will catch it.”


4) Published Rhythm

Weekly ops checks with a standing agenda. Ownership tagged on the board. “Work-in-progress” lanes visible to all. Visibility replaces supervision; leaders stop hovering because the system shows enough.


A composite scene (you’ve seen this movie)

A services firm grew from 18 to 46 people in eight months. New managers were hired. Tools were set up. Yet everything still slowed unless the founder “looked once.”


We didn’t add more meetings. We installed the middle:

  • Converted job descriptions into Role Charters with owned outcomes.

  • Introduced a Decision Ladder for sales and delivery.

  • Created two Escalation Windows a week.

  • Shifted standups to a Published Rhythm with explicit handoffs.


Week 1 felt slower … on purpose. By Week 4: fewer ad-hoc pings, shorter review loops, and most importantly, decisions moved without the founder’s “final glance.” The team didn’t need more people. They needed a leadership system they could see.


Control isn’t clarity

Founders often confuse presence with performance. Your presence is valuable when the system is young. As you scale, constant presence becomes distortion. People wait. They hedge. They hold back the last 10% because you might want to change it.


Leadership at 50+ isn’t about being in more rooms. It’s about designing exits from rooms  so the right decisions happen without you, and the right ones still find you on time.


How to start this week

One hour. Four moves.

  • Name the middle. List managers who should be catchers … owning closure, not just tasks.

  • Write one Role Charter. Pick your highest-friction lane. Clarify scope, decisions, and “done.”

  • Draw a Decision Ladder. What is green/amber/red for that lane? Publish it.

  • Schedule two Escalation Windows. Lock both into the calendar.


    Announce that late-night DMs are now the exception.

Run this for 14 days. Expect wobble. That wobble is your system learning to hold.


The takeaways

  • People add capacity. Systems add speed. Without the middle, headcount just multiplies coordination.

  • Visibility beats supervision. When ownership is public, leaders can be strategically unavailable.

  • Calm is scheduled. Rhythm isn’t bureaucracy; it’s how scale stops stuttering.


If this sounds like your Monday mornings, send it to the person who keeps the wheels turning when you’re in meetings. They’re your first catcher. Build around them.


(The writer is Co-founder at PPS Consulting, helping growth-stage founders install the leadership systems and operating rhythms their next stage demands. Views are personal. Write to rahul@ppsconsulting.biz)

 

1 Comment


rahul
Sep 11, 2025

Read more deep-dive insights at www.ppsconsulting.biz/blog.

Like
bottom of page